Private Beta

Join the AetherFS private beta.

AetherFS is for teams whose agents or users work on real file trees and where one VM per worker is starting to show up in budget, latency, or workflow complexity. The private beta is for teams ready to test hosted sessions against a real use case.

This is not a self-serve waitlist. It is a direct pilot path for teams who want to evaluate shared bases, copy-on-write sessions, and API-first session control with help from the team building it.

Request beta access Read the platform overview

Who should apply

Strong fit for teams with a real session problem.

You are building agent products that work on repos, notebooks, configs, or other real file trees.
Per-agent VM cost, duplicated clones, or idle workspace spend is already a real problem.
You want to pilot against hosted HTTP or gRPC first, with Aether CLI available when a mount is genuinely needed.
You can evaluate one production-shaped workflow instead of a toy demo.

What beta includes

A hands-on pilot, not just account access.

Direct rollout help

We work with you on the first pilot so the evaluation stays tied to a real workflow, not a synthetic benchmark.

Integration guidance

We help you choose the right surface for the pilot: HTTP, gRPC, or Aether CLI when local filesystem semantics are unavoidable.

Fast feedback loop

Private beta is the stage where workflow gaps, integration friction, and open questions should surface quickly and get discussed directly.

Pilot process

What to expect from a private beta engagement.

The goal is to evaluate one meaningful workflow and learn quickly. We are not trying to bury the pilot under a broad rollout before the fit is clear.

01

Intro and fit

We start with your workflow, current architecture, and the part of your stack where hosted sessions could replace duplicated workspace copies.

02

Pilot definition

We narrow the beta to one concrete workflow, define the preferred interface, and decide what success should look like.

03

Integration and trial

Your team pilots AetherFS in that workflow with direct support while we learn where the session model helps and where it still needs work.

04

Feedback and next step

We review the outcome, the economics, and the integration shape, then decide whether to expand the pilot or keep the scope tight.

What to send

Make the first email specific enough to shape a pilot.

The fastest way to start is to describe the workflow you want to test and where the current architecture is wasting time or money. That is enough to tell whether a private beta pilot makes sense.

Use the private beta contact link. If there is a fit, the next step is a scoped discussion around the workflow, the integration path, and the pilot boundary.

What your team is building and where agents or users touch real file trees.
Which workflow you want to pilot first.
Whether you expect to start over HTTP, gRPC, or with Aether CLI for local mounts.
What is hurting today: VM cost, clone time, coordination, review flow, or something else.
Rough team size and expected timeline for a pilot.

Join

Bring one real workflow. We can tell you quickly if the beta fits.

The fastest way to get a useful answer is to send one real workflow, the interface you want to try first, and the problem you want the pilot to prove or disprove.

Start here Email for beta access Send the workflow you want to pilot and the pain point you want to test. Workflow fit See workflow patterns Check whether your workflow matches the session model and lifecycle. Local path Read about Aether CLI See where local mounts help and how they fit into the hosted workflow.