EP

Getting in

Five ways to start

Start with who runs the organization data server. Those two paths come first. To try the product now, open Elastic Projects on itself. That path needs no account.

Set up your organization

An Organization Data Server keeps the files after people leave. Someone must run it. That is either us or you.

  1. Host your organization here

    Recommended

    Your organization gets its own address on this host. Projects answer on your-project.elasticprojects.com as signed atproto repos. Any client can verify them. Git can clone them. The organization owns the files.

    Hosting does not mean we own the organization. The organization keeps a rotation key we do not have. It can move to another host without our help.

    How hosting works

  2. Run your own Organization PDS

    For teams that want the machine

    Local pack runs the Spaces alpha PDS image on hardware you control. You need about 2 vCPU, 4 GiB of memory, and 20 GiB of disk. This runs a real Organization Data Server today.

    You own backups, upgrades, and uptime. The identity stays portable. You can start here and move to hosted later.

    The Docker pack

Try it first

Elastic Projects runs on AT Protocol Spaces. Spaces is alpha. Sign-in needs an account on a server that supports Spaces. Most Atmosphere accounts cannot do that yet. These three paths do not wait on that.

  1. Open Elastic Projects on itself

    No account needed

    The public demo is this product's own tree on this deployment. Pick a display name. Receive a guest identity. Pull, edit, and publish. Share links work the same way for private projects.

    The tree is world-readable and world-editable on purpose. Do not put anything there that a stranger must not read or change.

    Open the product tree

  2. Run it on your own machine

    About five commands

    Local preview includes a seeded organization, projects, and people. Pull files, edit them, and publish with no account. That is the fastest way to test the model.

    git clone <your-origin-url>
cd elasticprojects
npm install
npm run dev

    Open http://127.0.0.1:43147 and choose Open local preview. This public host hides that button. The preview seeds fake identities that do not belong in production.

    Full setup guide

  3. Sign in with a Spaces account

    If you already have one

    Enter your handle on the home page. Your server asks you to approve access. Elastic Projects never sees your password.

    If sign-in fails, your handle is on a server without Spaces. That is common today. Spaces is alpha. Most PDS builds do not ship it yet. Request an account on a server that supports Spaces from bsky.network/account, or read the Spaces alpha announcement.

    Go to sign in

Came from the Spaces announcement?

A space is a permissioned set of records in the members' own repos. You read them with a credential from the space authority. Elastic Projects makes that authority an organization DID. The space looks like a filesystem with paths, hashes, a working tree, and publish commands.

Files a company depends on must not belong to whichever employee created them. Today every atproto record still lives in a personal repo without an organization authority.

Spaces control access. They do not provide confidentiality. Members and the servers that hold the data can read it. Nothing is encrypted at rest. See the other limits.

Why can't I use my regular Bluesky account?

A project here is an AT Protocol space. It is one shared filesystem with a member list. The organization owns it. Spaces need a new server capability. Your handle works only if that server supports Spaces. Until it does, use the product tree demo or local preview.