Private beta

Tell us how your agents run.

The first beta cohort is for builders who already run coding agents through Cursor, OpenCode, Aider, or an OpenAI-compatible SDK.

Collects: Email, tool, spend range, demo interest
Does not collect: Prompts, project data, API keys
Next step: Manual review before account access

Founder access

Request a beta seat

Selected plan: Not sure yet

Email Primary coding-agent tool Estimated monthly coding-agent spend Plan interest We use this to route the first setup call. You can change it before sending. I want a Cockpit demo before live gateway access.

This opens a local email draft. Do not include prompts, API keys, bearer tokens, or project secrets. Email hello@flatfee.one instead.

Plan fit

Pick the beta lane that matches your work.

Solo Starter or Pro

One builder validating predictable spend for agent-heavy coding sessions.

Founder Pro or Power

A product team running daily coding agents and wanting receipt visibility.

Team waitlist Power or Scale

Multiple workflows, procurement questions, or a need for a guided Cockpit demo.

Why email first?

The beta is controlled until smoke auth, account setup, and support workflows have enough production evidence.

Can I register now?

Yes. Account registration exists, but beta access is still reviewed before live gateway use is enabled.

What should I not send?

Do not send API keys, bearer tokens, prompts, private code, or customer data in the intake email.