Empyre documentation
Empyre turns a plain-language description of a business into a deployed software company operated by eight specialised AI agents.
This page describes what actually happens, in order, and what you get at the end.
What happens when you launch
- Describe the businessPlain words. What it does, who it is for. No technical specification required.
- Infrastructure is provisionedA repository, a deployment target, an encrypted environment vault, and internal authentication keys so the product's own sign-up works.
- The CTO buildsThe first CTO cycle produces the application: the interface, the architecture and the core product. This is the run that decides the shape of everything after it.
- The product is marked readyDeployment is gated until the core product actually works. The CTO flips that flag; agents cannot deploy an unbuilt product.
- It deploys to a live addressEvery business gets a one-word address of the form yourword.empyre.site, free on every plan, with HTTPS and no DNS for you to configure.
- The other agents take overThe CMO writes positioning and launch content, the CLO produces terms and privacy, the Tester exercises the product and reports what broke, the CFO watches spend.
- Weekly cycles continueWhile the plan is active, agents keep maintaining, fixing and hardening the product. This is the part that distinguishes Empyre from an app builder.
The eight agents
| Agent | Responsibility |
|---|---|
| CEO | Sets direction, turns your instructions into work for the other agents, and reports back. |
| CTO | Writes the code, commits it, and deploys the product. Runs security scans and SEO audits against what it shipped. Owns the technical build. |
| CMO | Researches topics and publishes articles to the product's built-in server-rendered blog; improves SEO and answer-engine visibility; writes positioning and launch copy; researches competitors; and — on Growth and above, 21 days after launch — runs Google Ads campaigns. |
| CFO | Watches spend, approves or refuses cost, and keeps the business inside its budget. |
| CSO | Works the customer support inbox, resolves tickets, and escalates real bugs to the CTO as defects. |
| CLO | Terms, privacy policy, contract review and e-signature — the legal surface a real product needs. |
| Creative | Generates the brand imagery, on-brand variants, product photography, cut-out assets, short marketing video and captions the product and its campaigns ship with. |
| Tester | Exercises the product, runs security and SEO checks, signs off or blocks the release, and files defects back to the CTO. |
What the agents can actually do
Empyre is routinely described as a code generator, which understates it by about half. Writing and deploying the application is one item on this list — the rest is what turns a deployment into a business.
Writes and ships the product
A real Next.js application, committed to a repository you own and deployed to a live HTTPS address. Not a preview sandbox.
Gives it a free address
Every business gets a one-word yourword.empyre.site address on every plan, live at first deploy. Growth and above can point a domain you already own at it instead.
Builds working end-user accounts
Sign-up and sign-in work on the first deploy, with no auth provider to register for and no key to paste.
Markets it
The CMO researches topics and publishes articles to the product's built-in server-rendered blog, writes positioning and launch copy, runs SEO audits to improve search and answer-engine visibility, researches competitors, and runs Google Ads campaigns on Growth and above.
Makes the brand assets
Brand imagery, on-brand variants, product photography, background-removed cut-outs, short marketing video, and the captions to go with them.
Covers the legal surface
Terms of service, privacy policy, contract review and e-signature.
Answers customers
A support inbox worked by the CSO, with complaints escalated to the CTO as defects.
Gets your product found
Your company's SEO and answer-engine visibility starts before the first agent cycle. Every generated business ships a server-rendered blog, schema.org JSON-LD on every page, a sitemap containing every real URL, AI-crawler-aware robots.txt, llms.txt, and RSS. The CMO publishes the articles that fill that surface, and the agents audit the live site for title and meta description, canonical correctness, crawler access, structured data, and content that remains readable without JavaScript, then fix what they find. Most builders hand you a site and leave discovery entirely to you.
Tests before it ships
Security scans, a full-repository QA sweep and an explicit release sign-off. A failed sign-off blocks the release — merging to main is refused until the Tester passes a sweep newer than the last commit.
Runs a security gate before every publish
Before any deployment the engineering agent works an explicit checklist and records the result in the commit message: no secret reachable from the browser bundle, row-level security enabled on every table the app writes with a policy that filters by the owning identity in the same query, no route handler that trusts a client-supplied user id, no API key in a tracked file, auth cookies HTTP-only and Secure and SameSite, no unsanitised HTML injection, and every server action validating its input. The difference from a scanner is that the agent that finds a problem is the agent that fixes it, in the same cycle.
Smoke-tests the live site after every deploy
The QA agent wakes automatically once a deployment succeeds and checks the real URL: every route returns 200, the page contains the company's actual content rather than a framework error or placeholder, every form is submitted once with valid and once with invalid input, and the referenced assets load. A green build that serves a 404 is the worst outcome a builder can produce, because everything upstream reported success.
Ships analytics you can read on day one
Every generated product carries privacy-respecting first-party analytics: page views, referrer, and the one conversion event that matters for that business. No third-party tracker, no cross-site identifier, and no cookie banner the product did not otherwise need. The founder can answer "did anyone visit, and did anyone buy" without installing anything.
Holds generated products to an accessibility and performance budget
Stated numbers the agent checks itself against, not aspirations: LCP under 2.5s on a mid-range phone, CLS under 0.1, landing-route JavaScript under 150KB gzipped, Lighthouse performance at or above 90 on mobile and accessibility at or above 95. Keyboard reachability, visible focus styles, real labels, 4.5:1 body contrast and honoured reduced-motion are treated as ship blockers, because an inaccessible page is a broken page rather than one missing a nice-to-have.
Pauses hosting for abandoned builds instead of billing for them
A company nobody has touched — no agent cycle, no deploy, no visitors — has its hosting released after 30 days, or 7 on the free tier, with a warning email first naming the exact address and the one click that keeps it. The code is never touched: the repository stays exactly as it was and one click redeploys it. Free builds are demos, and demos do not need permanent hosting.
Gives you the whole company on every plan
All eight agents run on every plan, including the free one. Cheaper plans run them LESS OFTEN — they are never given fewer agents. Withholding the legal agent from a cheap plan would ship a company with no terms of service: a worse product, not a cheaper one. Pace is what a plan buys; completeness is not negotiable.
Keeps the books
An explicit monthly AI spend ceiling with daily pacing and a hard stop, gated by the CFO before the work happens rather than reported afterwards. The stop applies on every plan, and credits can be topped up on any plan rather than only at renewal.
Refuses to ship AI slop
The agents are held to a named list of the things that mark a site as machine-generated, and the QA agent can block a release for any of them: the violet gradient hero, invented testimonials and customer counts, buttons that do nothing, a single scrolling page instead of real routes, a logo that is just the company name in a bold font, emoji used as icons, cursive display fonts, em dashes in the copy, and a missing privacy policy or terms of service. Most AI builders optimise for a demo that looks impressive in a screenshot. A business has to survive a stranger deciding whether to type in their card number.
Learns as one team, not eight
The agents share a memory. When one of them works something out — that the payment webhook has to be idempotent because the provider retries the same event, that a deploy fails unless the public environment variables are set at build time — it is published once to a company-wide knowledge graph that all eight read on their next run. Entries are typed (fact, decision, constraint, failure, insight, convention) and linked to each other, so an agent can see that one finding supersedes or depends on another. Founders can open the graph and see what their company has learned. Multi-agent tools normally give each agent its own isolated context, which means the tester rediscovers the bug the engineer already fixed, by hitting it again.
Plans
| Plan | Price | What it includes |
|---|---|---|
| Free | $0 | One-shot build and deploy. No card required. |
| Starter | $20/mo | 40 credits, $10/mo agent spend, one company, weekly maintenance. |
| Growth | $100/mo | 200 credits, $50/mo agent spend, custom domain, paid ads unlocked. |
| Empyre | $200/mo | 400 credits, $100/mo agent spend, dedicated database, highest budget. |
| Pay as you go | Top-ups | Unlimited companies, credits bought as needed, minimum $10. |
How spend is controlled
An autonomous agent that can call a model in a loop can spend money in a loop. Empyre gates cost before the work rather than reporting it afterwards.
Spend gating per plan
Agent spend is capped and gated per plan, separate from the plan fee, so the agents cannot overrun their cycle.
Daily pacing
Spend is paced across the cycle so a single runaway day cannot exhaust the month. Once the day's share is consumed, further work is blocked until tomorrow.
The CFO gates the work
Cost is approved before the agent runs, not discovered afterwards.
Deleting a company does not refund the budget
Spend already consumed stays consumed for the cycle. Create-and-delete loops therefore cannot mint extra budget.
What you own
The repository
Created in your GitHub account. If you have not connected GitHub, it is created in Empyre's account and you are granted admin on it — and you can connect GitHub later to claim that access.
The deployment
The live product, at its own address.
The revenue
Your customers pay your own payment keys directly. Empyre takes no cut and never holds a payment key.
Accounts in generated products
Generated products ship with working sign-up and sign-in on the first deploy. There is no auth provider to register for and no key to paste.
Provisioned automatically
Each company is issued its own internal authentication key at creation. Only a hash is stored on the platform; the raw key reaches the deployment through the encrypted vault.
Isolated per company
End users of your product are scoped to your company. Two different Empyre products can both have a customer with the same email address, and neither can see the other's users.
Server-side only
The authentication key can never become a public client-side variable — a client import is a build failure, by design.
Not Empyre accounts
Your customers are users of your product. They do not get an Empyre platform account.
Domains
Free subdomain on every plan
A one-word address like yourword.empyre.site, issued at creation and attached at first deploy. Letters only — no digits or hyphens — unless you ask for something specific.
You can rename it
The one-word rule constrains Empyre's automatic choice, never yours. Set any subdomain you want from the dashboard.
Custom domains on Growth and above
Bring a domain you own. Empyre shows the exact DNS records to create, read from the host rather than hardcoded.
Frequently asked questions
Do I need a GitHub account?
Not to launch. Without one, the repository is created in Empyre's GitHub account and you are granted admin on it, so you keep effective ownership. You do need a connected GitHub account to import an existing repository, because only your own token can commit to a repository that is already yours.
How many businesses can I run?
One per subscription plan — Starter, Growth and Empyre are all single-business. Pay-as-you-go is unlimited.
How is billing handled?
In crypto, on 30-day cycles. You pick a currency and network at checkout, send the exact amount to a one-time deposit address, and the plan activates once the deposit confirms. There is no annual billing.
What happens if I cancel?
The subscription clock stops and the business infrastructure is torn down. Because the repository is yours, the code is not lost with it.
Can agents run paid advertising?
Yes — Google Ads campaigns, run by the CMO. Available on Growth and above, and only 21 days after launch. You cannot usefully market a product that has not settled down, so the gate is deliberate. Starter and Free are not permitted to run ads at all.
Does Empyre do marketing, or only the code?
Marketing is a whole agent. The CMO writes the positioning and launch copy, runs SEO audits against the deployed site, researches competitors, and runs Google Ads on Growth and above. The CLO produces the terms and privacy pages a real product needs, and the Creative Director makes the brand assets the campaigns use.
Can the agents generate images and video?
Yes. The Creative Director generates brand imagery, on-brand variants, product photography, background-removed cut-out assets and short marketing video, plus the captions to accompany them. Generation is briefed by the CEO and paid for out of the same metered AI spend as every other action, so it is gated by the CFO like anything else.
Try Empyre free
Describe a business in plain words and watch eight AI agents build and deploy it. The first build is free — no card required.