Requesting access.
Essarion is in private beta. We onboard teams in waves so we can stay close to each one. This page is the short version of how to put your name in, what we're looking for right now, and what to expect after the invitation lands.
§ 01Private beta
Invitations roll out weekly. Teams that come in during beta typically get a workspace with seats for the people doing the work, an API key for whoever's integrating, and a modest call quota that's enough to put the platform through real use without committing to a plan before you've seen the surface.
Beta isn't a free trial. It's a working relationship — we ship quickly during this phase and we want to ship in a direction that makes the platform better for the people actually using it.
§ 02What we ask
One paragraph is enough. Tell us how you'd use the platform: what depth of research you need, which agents you'd run, whether you're integrating Essarion behind your own product or sitting in the workspace yourself. The more concrete, the better — "we'd run weekly competitive briefs against ten public-equities filings" lands better than "we want to try AI."
§ 03Who's a fit right now
Three kinds of teams are getting the most out of the platform today.
- Analyst & ops teams who need defensible synthesis — bibliographies that survive a reviewer, not chat transcripts.
- Executive workflow teams running diligence, contract review, board prep, deal underwriting, or anything else where the output has to be defensible to someone who didn't write it.
- Integrator and platform teams embedding research or agent capabilities into their own product, behind their own auth.
If you're looking for a casual chatbot, Essarion is not the right fit yet. The platform is built around projects, runs, and audit trails — overhead that pays for itself when the work matters and gets in the way when it doesn't.
§ 04How to ask
Two paths, both fine.
- Web — fill in the request-access form on the homepage at essarion.com. It takes about a minute.
- Email — write to access@essarion.com. Include the same paragraph from above.
§ 05What happens after
If we have a slot in the next wave, you'll receive an invite code by email. The code unlocks sign-up; from there the platform walks you through creating a workspace and your first project. Your first API key is issued from the keys panel — see API keys for the lifecycle.
Design partners — teams we're shaping the product with — also get a one-on-one setup call. We use it to understand your workflow well enough to be useful from day one, not to upsell you.
§ 06While you wait
The docs are open. Two pages worth reading first:
- Architecture — how the pieces compose, where data lives, where control lives.
- API · Quickstart — the shape of a real integration, end to end.