Trust
Trust you can check.
ForgeOS only does what you allow. It writes down everything it does.
Each power is a separate yes.
Reading is not writing. Writing is not going live. No yes, no action. You can take any yes back (in your workspace).
ForgeOS takes no consequential action outside your project on its own authority: going live, spending money or contacting anyone waits for your yes. Inside your project, a project it created for you finishes itself unless you turn that off. Deploy is its own decision.
When unsure, it stops.
It asks you
It waits for your call. It never guesses or retries quietly.
A second AI reviews
A model that didn’t write the change reads it — on the free open-source models too, since 2 September 2026. If no reviewer can be found, the build says so rather than implying a reviewer ran.
No clashes
Two jobs can’t change the same files at once.
A record you can’t edit
Each step is chained to the one before. Changing history breaks the chain. A model’s report about itself is shown as a claim, not proof. See status.
What we measured — good and bad.
How we measured
Audited broad-build cohort, measured 2026-09-01: 641/932 verified end to end (68.8%; descriptive 95% interval 65.7%–71.7%), 143/932 false successes (15.3%; 13.2%–17.8%). 1005 total builds; 59 invalid-task rows and 14 unverifiable rows excluded. Repeated tasks are correlated. This is retained historical evidence, not qualification of current main. The production false-success limit remains 2%; the release gate is not satisfied. How these figures are measured (raw data, JSON).
Your data stays yours.
Not shared
Your work is never pooled with other customers.
Customer data is off
Connecting a repo doesn’t turn it on. Only you can.
You pick providers
Choose which AI providers may run work.
What free models keep
Some free AI providers don’t say what they keep (undeclared retention). We ask you once, at your first build, before any of them sees your work. Details
Take it with you
Export what your workspace holds any time (in your workspace); your code downloads from the project menu. Secrets, sign-in secrets, uploaded file bytes and internal support notes are not in the export; the privacy notice lists every section and how to ask for the rest.
What ForgeOS will never do
- Sell your work, use it for advertising, or train our own models on it. The privacy notice says which outside services we cannot promise this for, and asks you first.
- Spend past the limit you set. When free models run out for the day, work stops; it never switches to paid.
- Change your project, publish, or go live without your yes.
- Push to your branches or merge for you: it writes its own branches, and you choose.
- Keep you: export everything, any time, from your workspace.
- Call something done that it did not check: every result says what was checked and what was not.
If someone is in crisis
- When a message talks about suicide, self-harm, abuse, violence or a medical emergency, Ember answers with care and lists support lines under its reply: your local emergency number first, then crisis lines for the language you wrote in (988 in the US and Canada, Samaritans on 116 123 in the UK and Ireland, and others), and findahelpline.com for everywhere else.
- If no AI model can answer, or a model refuses, ForgeOS writes the reply itself, so the support lines are always there. Ember on this website does the same, without asking a model.
- Ember never gives details about methods, doses or means. If a model’s reply does, ForgeOS shows its own words instead.
- A message like that is never turned into a reminder, and Ember never offers to remember it.
- In a chat that isn’t about a project, Ember says it is an AI, not a person, when the chat starts and every three hours after that. In any chat, it says so whenever you ask.
- We count how many times the crisis lines were shown, one number per day, to report it. The count holds a date and a number, nothing you wrote.
- Ember is not a therapist or a crisis service, and it cannot call anyone for you. If you are in danger, call your local emergency number.
What we do not claim
It looks, but does not decide
It can look at a picture, but nothing is stopped by what it sees. A vision model writes down what it thinks, and that verdict is recorded, not enforced. For anything visual, look at it yourself before you publish.
Your checks, not ours
You describe an outcome. ForgeOS plans it, builds it and runs your own checks, then shows its work. It runs your project’s own tests. It does not add security or accessibility checks of its own. It goes live at a plain web address you choose, only after your yes. Putting it on your own servers is not connected yet. Your first screen says which models this instance has ready.
No certification
We don’t certify your compliance. We have no audit report.
No promise it’s correct
We tell you what was checked, not that it’s right.
No uptime promise
We haven’t measured long enough to make one.
No hidden actions
It can’t take a big step outside your project without asking.
The privacy policy is in force since 2 September 2026. The terms, dated the same day, are a draft awaiting the company’s details: [MAILING ADDRESS] and [STATE] are still placeholders. To be clear: neither has been read by a lawyer, and no lawyer stands behind them.