Experimental demo on a sample page. Not production-certified. Visitors never cause a paid AI call.
Experimental · Sample page

A real small software factory

This is a real small factory: your AI writes a small change to a sample page, Atlas really tests it, only you can approve it, and it goes live with proof.

What this proves

  1. Tests decide, not the AI. If the AI's change breaks the page, Atlas catches it and won't let it through. The tests show your change passed these specific checks. They don't prove it has no defects.
  2. A person stays in charge. Nothing ships until you click Approve. The server enforces this, outside the AI's control: your AI has no approve tool, and it can't press the button for you.
  3. There's proof. The receipt ties together exactly which code was tested, what the results were, and who approved it and when. Anyone can check it, and if anything changed afterward, the check fails.
  4. It's real. Your change goes live at its own link.

Bottom line: AI can do the work while you keep control and have a record you can show anyone.

This demo works on a sample page. Your change goes only to your own copy, at its own link. The real site is never touched. It is experimental and not production-certified. Visitors never cause a paid AI call.

Next: Atlas decides

Atlas, the AtlasClose Magistrate, a fluffy coastal dog by the beach
Atlas · The Magistrate

How to connect

In your AI app, add a connector with this address. You don't need an account, a sign-in, or a key.

Connector address

https://demo.atlasclose.com/factory/mcp

If you use ChatGPT, refresh its tools once so it sees the new links. You can do the same in other apps if the tool list looks empty or out of date.

Things to type

In the chat, ask for a small change to the sample page. For example:

add a phone column to the sign-in sheet
make the title bigger
add a notes column to the sign-in sheet

These are sample requests. Your AI's first reply will give you a watch link. Open that link before you go on.

The five steps

Each run follows the same path. A failed test is a real result: the watch page says why, and you can try again.

1

Ask

In your own AI chat, connected to AtlasClose, ask for a small change to the sample page.

2

Build

Your AI writes the full changed page (HTML and CSS only) and sends it with atlas.factory_submit. Atlas stores the exact bytes, their fingerprint, and what changed. No paid AI call on our side.

3

Test

Atlas runs real checks on the stored page. It reads the page and never runs it: valid HTML, no scripts, nothing loaded from outside, the sign-in table kept, and the change matches the request. If a check fails, the watch page says why, and your AI can try again (3 tries).

4

Approve

The watch page shows a preview and an Approve button. Only you can click it, in your browser. The server only accepts it from the watch page, for exactly the version that was tested. If the AI changes the page after you approve, your approval no longer counts.

5

Ship

Atlas checks that the stored bytes are exactly the version that was tested and approved, then puts them live at their own link (your copy only). Each time you open the receipt, it re-checks everything, including the bytes the live link serves.

What you'll see

These are sample pictures of the watch page and the receipt, using sample data only. They are not a live case.

https://demo.atlasclose.com/factory/mcp?watch=w-sample-1842

Sample mock · Live watch page

AtlasClose MCP · Live watch

Software factory

Atlas · The Magistrate
Experimental and not production-certified. Visitors never cause a paid AI call. All data on this picture is sample data.
Sample case

Add a phone column to the sign-in sheet

Sample case fc-sample-1842. Live: this page follows the case as it happens.

Live
  1. 1. AskSample request taken in: add a phone column to the sign-in sheet.
  2. 2. BuildThe visitor's AI sent the full changed page. Atlas stored the exact bytes and their fingerprint. No paid AI call on our side.
  3. 3. TestAtlas ran real checks on the stored page. The first try failed. The second try passed.
    Try 1 failed. 2 checks failed: the page had a script tag, and the sign-in table had no Phone column. The AI can try again.
    Try 2 passed. 9 of 9 checks passed, including the new Phone column.
  4. 4. ApproveA preview is ready. Only the person can click Approve, in their browser. The AI cannot approve.
    Live preview · sample page
    NameEmailPhone
    Sample Visitor Avisitor.a@example.com555-0100
    Sample Visitor Bvisitor.b@example.com555-0101

    Sample names only. The Phone column is the new change.

    Sample mock only — this button is not live. On a real run, only you can click it in your browser.
  5. 5. ShipWaiting for the person's approval. After ship, the changed page goes live at its own link (this visitor's copy only), and the receipt link appears.
https://demo.atlasclose.com/factory/mcp?receipt=frr-sample-1842

Sample mock · Receipt page, after ship

AtlasClose MCP · Software factory

AtlasClose receipt

Atlas · The Magistrate
Experimental and not production-certified. All data on this picture is sample data.
Receipt checks out. Re-checked just now: the code fingerprint, the tests re-run on the stored code, your approval on the record, the record chain, and the bytes the live link serves all match.
Sample receipt

Add a phone column to the sign-in sheet

The changed page is live at its own link. This is the visitor's own copy only. The real site was not touched.

Receipt
frr-sample-1842 Sample
Case
fc-sample-1842 Sample
Shipped
Nov 13, 2026, 11:18 AM PST Sample
Approved by
The person, in their browser, at Nov 13, 2026, 11:17 AM PST Sample
Tests
9 of 9 checks passed on try 2 (try 1 failed: a script tag, and no Phone column). These checks show the change passed them, not that it has no defects. Sample
Code fingerprint
sha256 sample 9c4e1a77b2d08f63a1c5e90b47d2aa18e6f0c3b5d1847a29c0e5b8f1a7362d4c
  • Each visitor's change goes only to that visitor's own copy. Nobody can change the real site through this demo.
  • This demo works on a sample page. It is experimental and not production-certified.
  • The approval is enforced by the server, outside the AI's control. The tests show a change passed these specific checks. They don't prove it has no defects.