diff --git a/ARCHITECTURE.md b/ARCHITECTURE.md index a7985bd..8ac924f 100644 --- a/ARCHITECTURE.md +++ b/ARCHITECTURE.md @@ -1,6 +1,6 @@ # Architecture -Cloudfall is the operator's record for a small fleet run by an AI agent. +Cloudfall is the operator's record for self-hosted servers run by an AI agent. The agent decides, Ansible executes, and Cloudfall sits between them: it declares what the agent may do, checks every result, and keeps the evidence behind every decision. Ansible is the hand, the agent is the brain, diff --git a/README.md b/README.md index b46dbec..36114c1 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # Cloudfall -Cloudfall is the operator's record for a small fleet run by an AI agent. +Cloudfall is the operator's record for self-hosted servers run by an AI agent. The agent decides; Ansible executes; Cloudfall says what the agent may do, checks every result, and keeps the evidence. Every operation has a verify step and every decision an audit entry: what the fleet looked like, what diff --git a/docs/brownfield-design.md b/docs/brownfield-design.md index 8ff3c79..35d26e5 100644 --- a/docs/brownfield-design.md +++ b/docs/brownfield-design.md @@ -9,7 +9,7 @@ longer declared by Cloudfall, it is read from Ansible. ## The product -Cloudfall is the operator's record for a small fleet run by an AI agent. +Cloudfall is the operator's record for self-hosted servers run by an AI agent. Point your agent at the Ansible repository you already have. Cloudfall turns your playbooks into a tool list, checks every result, and keeps the diff --git a/docs/logging-service-guide.md b/docs/logging-service-guide.md index ea4bb97..41a4082 100644 --- a/docs/logging-service-guide.md +++ b/docs/logging-service-guide.md @@ -14,13 +14,13 @@ open no additional listening port; metrics are pushed through the same mTLS gateway to Prometheus's remote-write receiver on the backend host. This stack is where the operator's signals come from. Cloudfall is the -operator's record for a fleet run by an AI agent, and the record needs -evidence to act on: a declared `AlertRule` firing here is what triggers a -proposal, the same gateway's read-only alerts route is what the operator -and the agent read, and an alert that stops firing is how an approved -remediation is verified (see the [operator guide](operator-guide.md)). -Without this stack the operator has nothing to watch and nothing to verify -against. +operator's record for self-hosted servers run by an AI agent, and the record +needs evidence to act on: a declared `AlertRule` firing here is what +triggers a proposal, the same gateway's read-only alerts route is what the +operator and the agent read, and an alert that stops firing is how an +approved remediation is verified (see the [operator +guide](operator-guide.md)). Without this stack the operator has nothing to +watch and nothing to verify against. ## Safety boundary diff --git a/docs/neon-migration-guide.md b/docs/neon-migration-guide.md index 3138ec3..e4ee5e8 100644 --- a/docs/neon-migration-guide.md +++ b/docs/neon-migration-guide.md @@ -6,13 +6,13 @@ there is no blueprint to import: Neon hosts only your database, so the config is written by hand and the migration is a guided dump-and-restore with the same tooling the Render path uses. -What you get in exchange for Neon's console is the record. Cloudfall is -the operator's record for a fleet run by an AI agent: the migration ends -with a receipt whose per-table row counts are the proof it worked, every -backup afterwards writes a receipt and a timer-driven drill proves it +What you get in exchange for Neon's console is the record. Cloudfall is the +operator's record for self-hosted servers run by an AI agent: the migration +ends with a receipt whose per-table row counts are the proof it worked, +every backup afterwards writes a receipt and a timer-driven drill proves it restorable, and the always-on operator watches the database with the -evidence attached to every decision. Managed PostgreSQL is mostly -insurance; this keeps the coverage and makes the proof yours. +evidence attached to every decision. Managed PostgreSQL is mostly insurance; +this keeps the coverage and makes the proof yours. > **Status:** the guided data migration (`cloudfall data copy`) is > proven live against an external managed PostgreSQL — dump, restore, diff --git a/docs/render-migration-guide.md b/docs/render-migration-guide.md index e7ac78f..23f83c9 100644 --- a/docs/render-migration-guide.md +++ b/docs/render-migration-guide.md @@ -6,14 +6,14 @@ what needs manual work, and the vocabulary differences between the two platforms. It is also the greenfield way into Cloudfall. Cloudfall is the operator's -record for a fleet run by an AI agent; a team that already has servers and -Ansible brings them (the [brownfield design](brownfield-design.md), not -built yet), and a team leaving a PaaS gets a fleet this way. Either way the -result is the same: every step below leaves a receipt, the migration ends -with an audit rather than a green light, and the always-on operator takes -over afterwards with a record of everything it does. An agent can drive -the whole guide through `cloudfall mcp serve`; the proving run did, through -its predecessor `cloudfall-mcp`. +record for self-hosted servers run by an AI agent; a team that already has +servers and Ansible brings them (the [brownfield +design](brownfield-design.md), not built yet), and a team leaving a PaaS +gets a fleet this way. Either way the result is the same: every step below +leaves a receipt, the migration ends with an audit rather than a green +light, and the always-on operator takes over afterwards with a record of +everything it does. An agent can drive the whole guide through `cloudfall +mcp serve`; the proving run did, through its predecessor `cloudfall-mcp`. > **Status:** proven live. An application actually hosted on Render was > cut over with its data and a real DNS flip on an owned domain, driven by diff --git a/site/public/index.html b/site/public/index.html index ca38b39..afa46b8 100644 --- a/site/public/index.html +++ b/site/public/index.html @@ -3,11 +3,11 @@ -Cloudfall — the record behind your AI operator - +Cloudfall — the record behind your self-hosted AI operator + - - + + @@ -15,10 +15,10 @@ - + - - + + @@ -216,7 +216,7 @@ "@type": "SoftwareApplication", "name": "Cloudfall", "url": "https://cloudfall.dev/", - "description": "The operator's record for a small fleet run by an AI agent. Cloudfall moves a SaaS's applications and databases onto one or two Debian servers you own, an always-on operator runs them, and every decision leaves evidence that answers why. No Kubernetes.", + "description": "The operator's record for self-hosted servers run by an AI agent. Cloudfall moves a SaaS's applications and databases onto one or two Debian servers you own, an always-on operator runs them, and every decision leaves evidence that answers why. No Kubernetes.", "applicationCategory": "DeveloperApplication", "operatingSystem": "Linux", "license": "https://www.gnu.org/licenses/agpl-3.0.html", @@ -253,8 +253,8 @@
Migration and operator proven live · open source · AGPL-3.0

Your servers, run by an agent.
With a record that answers why.

- Cloudfall is the operator's record for a small fleet run by an AI - agent. It moves your applications and data onto one or two servers + Cloudfall is the operator's record for self-hosted servers run by an + AI agent. It moves your applications and data onto one or two servers you own — hardened baseline, monitoring, health-gated deploys with rollback, a real DNS cutover — and an always-on operator runs them there. Every operation is verified, every decision leaves evidence: diff --git a/site/public/manifesto.html b/site/public/manifesto.html index e372c72..932532c 100644 --- a/site/public/manifesto.html +++ b/site/public/manifesto.html @@ -15,7 +15,7 @@ - + diff --git a/site/public/og.png b/site/public/og.png index 06c0030..f8da5ca 100644 Binary files a/site/public/og.png and b/site/public/og.png differ