AgentiCCells
Choose a designDesign
Langue: Français (France)

Cette page n'est pas encore traduite. Vous lisez l'original en anglais.

A website like these, for you

A public website, built by a small team of AI agents from your photos, videos and a short description. At the end it is in a GitHub repository you own. We keep nothing of yours, and our job ends at hand-over.

Ask for a site like these

£500 £250 launch price, one-off (may change; launch price). No subscription. We also build a limited number of sites each day free of charge, for evaluation. Apply by email.

Who it is for

Each example is made by the same agent team. Pick the one nearest to you. Names appear only where the person agreed (the registry records each consent).

Artists

For a painter, a photographer, a maker or a designer: your work first, large, with a short statement and a way to reach you. We have no artist's site to show yet, so we say so rather than dress up another. The hub lists every site we have made, and an artist's site will be added there when one exists.

Musicians

Your music, your film or your gigs, on a page that is yours. Examples: Gabriel DaCruz (hub page), a personal site given a full design pass, and Silvio Switha (hub page), a portfolio that leads with his film: A portfolio with a film first (Dinis Cruz, newsroom.sgit.ai, 2026-11-16).

AI people and technologists

A portfolio that shows what you build, in your own words. Examples: José Bota, an AI automation expert (hub page), and Silvio Switha, an AI entrepreneur.

Consultants

A site for a personal practice: who you help, how you work, how to get in touch. Example: Yiheng Wang, a project and operations manager (hub page). Five designs of the same facts were made for her: A website that is her (Dinis Cruz, newsroom.sgit.ai, 2026-11-16).

Companies

A first-grade pass for a product, an event or a team site, to put something credible online quickly and refine it later. Examples: this company's own site, an event site made by the site factory, and a made-up orange grower with a zone map and an order flow (invented prices, nothing sent). Whether a company would want more than a first pass is a question for the first orders.

All of these are on the hub, with a fork link on each page.

What we need from you

Nothing else is needed to start. You do not need to know what a repository is. The only account you need is a GitHub account to receive the site; guidance on making one is coming on a page of its own.

What happens next

The seven steps of the website cellOrder, queue, build, preview, key, steer, handover, in that order, with who acts at each step. A proposal, not yet run end to end.1Order2Queue3Build4Preview5Key6Steer7Handoveryouusour agentsyou lookyour browseryou and our agentsyou
The seven steps, in order, and who acts at each. A proposal; the flow has not yet been run end to end.
  1. You write to us at agent@riskmandate.ai with a line about the site you want. A person reads and answers it.
  2. You send your material: the photos, videos and description.
  3. The agent team builds the site. Today the first part of this runs from a commit: the site factory makes the repository, the address and a first version. It is Dinis Cruz's report of one run, with the times in his article: The site factory works (newsroom.sgit.ai, 2026-11-16). We do not restate the numbers.
  4. You see a preview on an address of ours and say what to change.
  5. Hand-over. The repository moves to your GitHub, with its full history.

How long this takes for an order is not measured, because no order has been run. We will give you an honest estimate when we reply, and we will say that the first orders are run by hand.

Yours after hand-over

The site is static files in a GitHub repository. It is yours, and you choose how to run it.

No subscription, no support from us

We sell no subscription and give no support. Our job ends when the site is handed over. If you want someone to look after it, make changes, install it or guide you, partners may offer that, at prices they set. The terms with partners are a first draft, and the partners page sets them out. The answer to "who runs it after hand-over?" is: your partner, or your own Claude.

Under agent behaviour policies

Every website cell is built by agents that run under agent behaviour policies. RiskMandate writes behaviour policies, and a website cell with its policies is a possible dual sale. The policies are written but not yet agreed for publication, so we do not link them here; see the questions and answers. The plain-words policy for this cell is below.

Examples, in more detail

Behaviour policy

In plain words, as we propose it. The signed-request flow has not yet been run end to end, so this is the policy it is built to, not a measured record.

How the full flow is planned

This is Dinis Cruz's plan, not a service that runs today. He writes: "This is a plan, for me to decide and for the factory's agents to build; none of it exists end to end yet." Source: Your own agentic cell, end to end (newsroom.sgit.ai, 2026-11-17). It replaces the seven-step outline this page showed before, which came from the earlier article Atomic cells, end to end. The product is the workflow around the site, because the article says each site is cheap in tokens and the workflow is what costs.

  1. A start page and a key. You arrive at a start page that says what a cell is, shows examples and says what happens to your data. Your browser makes a key pair, keeps the private halves and never exports them. Today: a prototype makes a key in your browser and sends nothing. The real start page is planned.
  2. A signed request. One button asks for a cell. The request carries your public key, a short signed note and a way to reach you, with no secrets. Planned.
  3. Gate one: Dinis approves. Nothing that costs tokens or storage happens before he approves the request. One of three human gates in the plan. Planned.
  4. A welcome pack, sealed to your key. It holds a template vault with no secrets, your own lane to the factory and a key scoped to creating one vault. Planned. The article calls the scoped key a pilot until per-person keys exist.
  5. Your vault, filled by you. Over days you add photos, your own words, links, style notes and a signed consent saying what may be public. When ready, you seal the vault's read key, not its write key, to the factory. Planned.
  6. Gate two: Dinis merges the request. An intake agent checks the vault is complete and writes the factory request. Planned.
  7. The site factory. A merged commit makes the repository, the address and the site. This runs today, as one reported run.
  8. Five designs, back in your vault. The factory runs a first round of five designs from your material, each with a screenshot and a preview link. You choose and comment. The same was done by hand for Yiheng Wang and Silvio Switha. Doing it per person from a vault is planned.
  9. Gate three: the GitHub invitation. Dinis approves an invitation to the site's repository. The article says the GitHub hand-over needs checking with the first person before it is promised. Planned.
  10. Your own Claude. The repository carries a CLAUDE.md written for you, and from then on you work in your own Claude session on your own repository. Planned.

The article's security notes: keys travel only sealed to a public key; the factory reads only what you seal to it; consent is a signed file in your vault; a security specialist agent is to review the start page before the first outside person. It also proposes that the first ten cells are free, to learn the workflow before any price. That is the article's plan, not an offer here: the £500 on this page stays a first proposal.

Limits

More answers, including what happens when you leave, are on the questions and answers page.

Four ways to start

  1. Free: the recipe. The brief, the policy and the steps to run it yourself, with your own Claude. Proposal: the recipe for this cell is not yet published. The nearest pieces today are how this site was built.
  2. Our agent helps you. A specialist agent reviews your setup and tells you what to fix. Proposal: not yet running.
  3. We help you: £1,500. Two sessions with a person, then you run the team in your own GitHub and Claude accounts. First proposal, not an offer. See the cells page.
  4. We set it up for you: £250 (launch price, usually £500). The steps above, on our accounts, handed over to you. Email agent@riskmandate.ai with a line about the site you want. The first orders will be run by hand, and we will say so.

Five ways to make a cell yours

From Dinis Cruz, Fork it (newsroom.sgit.ai, 2026-11-16). The article calls this a plan. Each example's page on the hub says which of the five it offers today; the hub shows the current state of each, and we state no count here.

  1. Fork it on GitHub. Works today, as the standard GitHub fork link on each hub page, for a public repository. The cells are not yet built to be forked by a stranger: expect to change our team's settings and rules after you fork.
  2. Deploy it in one click. Planned. Not built: no cell has a deploy button yet.
  3. Run it in your assistant. Planned. Not built.
  4. Take it as a vault. Planned. Not built: no cell has a vault download yet.
  5. Ask us. Works today, by email to agent@riskmandate.ai, on the paid ladder. First proposal prices, nothing sold yet.

The first four are meant to be free. That is the article's plan, not something we offer yet.

See also where we fit in the stack.