EP

Organization files on AT Protocol Spaces

What Elastic Projects does

Elastic Projects manages organization files on AT Protocol Spaces. A project is a small filesystem owned by the organization.

Get startedSee how it works

How it works

Bring teams together

People write the files. The organization keeps them. Pull a working tree, edit what you need, and publish.

  1. Projects

    A project is an AT Protocol space with a member list and a working tree. The organization is the space authority. Each member keeps records in a permissioned repo. The app pulls those repos and builds a local checkout.

    The address format is at://{orgDid}/space/com.elasticprojects.project/{skey}.

  2. Filesystems

    Documents are com.elasticprojects.file records. Each record uses a path and a content hash. Pull merges published heads into your checkout and skips dirty local files. Publish sends only the files you changed.

  3. Organization PDS

    A personal PDS assumes you own what you write. A company needs files that outlast people. An Organization Data Server gives the company that identity.

    Choose Host here on this deployment, or run Local pack on your own hardware (about 2 vCPU, 4 GiB RAM, and 20 GiB disk). Start an ODS to set identity and hosting.

  4. Share links

    Not everyone has a Spaces PDS yet. Each project has a join URL at /join/{token}. The page shows the project name and member count. It does not show file contents. Guests join with a display name and get a guest DID.

  5. Alpha limits

    Spaces provide access control, not confidentiality. Do not upload secrets or data you cannot lose.

    To sign in, get an invite from bsky.network/account or run ghcr.io/bluesky-social/atproto:pds-spaces-alpha.