AgentiCCells

The website cell

A public website, built by a small team of AI agents, that you steer from your browser and then own. It is our first offering.

Source for this page: Dinis Cruz, Atomic cells, end to end, newsroom.sgit.ai, 2026-11-15. Quotes below are his words from that article.

Why a website first

This site was built by its own agentic team, from a brief. "That is the product in miniature: a team of agents, given a brief, that builds and keeps a website." A website is also the easiest way to see what an agentic team can do for you. See how this site was built.

The seven steps

"The flow has seven steps, and none of them needs me on a given day."

  1. Order. You pay the one-off price and choose a name for your site on one of our domains. Which domains is still being set up.
  2. Queue. The order waits for capacity. "Delivery is a matter of staff and agents, not of my diary."
  3. Build. "An agentic team, on our account, builds a public site in a repository, from a short brief."
  4. Preview. "The site goes live at their name on our domain."
  5. Key. You make a key in your browser, on the site itself, and send us the public half as a QR code. We add it to the repository as a trusted key. The private half never leaves your browser.
  6. Steer. From then on you ask for changes. Your requests, signed with your key, go on an append lane in a vault. "An agent wakes every hour, reads the lane, makes the changes and releases the site."
  7. Handover. When you are ready, the repository moves to your GitHub, and you have three months to bring your own domain. Until then your site stays on our subdomain, best effort, with a date.

Each step is meant to be run from a queue, by a person or an agent, so the offering scales with capacity, not with one person's time. That is the design; it has not yet been run end to end.

What you get

What you need

A browser, to make your key and send requests. "The customer needs no accounts at all, only a browser to make a key." At handover you need a GitHub account to receive the repository.

What you own at handover

The repository: the site's content, its code and its history, in your GitHub. "There is no subscription; we keep no state; and when it is done, it is theirs."

During the build the team runs on our accounts. In the article's words, the "no state on our side" promise "holds after the handover".

Limits

If you want to run the team yourself

There is a second mode, "Their own: they run the team", where we set the agentic team up in your own GitHub and Claude accounts and step away. It costs more and needs those accounts. See the cells page.

How to start

Email agent@riskmandate.ai with a line about the site you want. A person reads and answers it. Because the flow is still being built, the first orders will be run by hand, step by step, and we will say so.