What the platform does#
Atlas Venture Studio's platform turns an idea into a live offer page, measures who saw it and who committed, and ends every test with a recorded verdict. It is version 1: one operator (Jason) runs everything from this console. Builders, partners and buyers only ever see public pages.
Who uses what#
| Person | What they use | How they get in |
|---|---|---|
| Operator (Jason) | This console at /console — every routine action |
A magic link by email, then an authenticator code |
| Builder (someone with a prototype) | The studio site: Home, How it works, Apply | Public |
| Partner (a builder whose idea is being tested) | A private outreach page at /o/<token> |
A secret link the operator sends; no login |
| Buyer (a prospect or a member of the public) | An experiment page on its own subdomain, e.g. ledgerfix.atlas-venturestudio.com |
Public, usually through a personal or tagged link |
How the platform is built to behave#
- One application. The studio site, every experiment page, the forms, the partner pages and the console are one app on one domain,
atlas-venturestudio.com, with one database. - Launching is a button. Creating, publishing, pausing or closing an experiment never needs a deploy or a DNS change. A published page appears on its subdomain immediately.
- Live tests are frozen. Publishing stores the page as a snapshot. Buyers always see that snapshot, so neither a code change nor a brief edit changes a live test. Only Republish, with a stated reason, changes the page, and that is recorded.
- Evidence over activity. The platform records who saw an offer (visits), who responded (leads), what partners did (outreach) and what was committed (events), and shows it against thresholds set before the test.
- People decide. The platform never suggests a verdict. The operator records continue, revise or stop, with a memo.
- Experiment 000 is the studio itself. The studio's own builder recruitment is measured like any experiment: studio-page visits and applications count under experiment 000 (slug
studio). - One design everywhere. The console, the public pages, experiment pages (templates v2 and v3) and the emails share one visual system, "Meridian".
How to use this guide#
The pages on the left follow the life of a test.
- Start here explains the concepts, signing in, and how the console is laid out.
- What the public sees covers every page a builder, buyer or partner can reach, and the emails the platform sends.
- Running experiments walks through each console screen, field by field and tab by tab.
- People and data covers deletion requests and what the nightly job does.
- Workflows and reference strings it together as click-by-click procedures, and lists the rules the platform enforces.
Use Search at the top of any guide page to find a field, a message or a rule. Every heading has a link (hover it for the #) that you can copy and share.