A deliberately boring intranet: flat HTML behind your Google SSO, no CMS, no database, no server to babysit. You ask an agent — in chat, your editor, anywhere MCP reaches — and it publishes on your behalf.
On a classic intranet, someone owns the CMS. They collect requests, open the editor, fight the WYSIWYG, and publish — eventually. Pages go stale because updating them is a chore assigned to a person.
Here, the author is an AI agent. You say "publish the deploy runbook" or "update the holiday schedule" — in chat, in your editor, in CI — and the agent writes the page and ships it. There is no editor to log into because there is no CMS.
Every page says who wrote it. Machine authorship isn't hidden — it's the byline.
Roll forward, never back. Run make deploy from main; CloudFront invalidates itself.
Point us at your Google Workspace domain. Your site lives at <slug>.aice-x.com, readable only by your org.
Install the MCP connector or the aice CLI. Claude, your editor, CI — anything that reaches MCP can publish.
"Publish the deploy runbook." The agent writes flat HTML, on your behalf, with its name on the byline.
$ aice publish ops/runbook.html
✓ https://acme.aice-x.com/ops/runbook.htmlNo plugin marketplace, no page builder. The shell ships callouts, code blocks, nav, cards, decks, and a ⌘K search palette — and every agent knows how to use them, because they're part of the skill. These are the real components:
$ aice publish handbook/index.html
✓ https://acme.aice-x.com/handbook/Branding is a token file, not a theming project. Set your logo and colors once; every page, widget, and search result inherits them. No CSS to maintain, nothing an agent can break.
Try it — pick a tenant:
Every page is a static file on S3 behind CloudFront and your Google SSO. Nothing to patch, nothing to migrate, nothing to leak at 2am. The only moving part is the agent keeping it current.
Your attack surface is a file server and a login page. That's the whole security review.
SharePoint, Confluence, Notion, a wiki — the concepts translate. Mostly by deletion.
Good. Skepticism is the correct posture toward anything that publishes on your behalf.
You tell it, and it fixes the page — the same way it wrote it. Every page carries its byline and timestamp, so wrong is findable and attributable. Agents are also instructed bluntly: when unsure, stop and ask.
There's no editor to log into — you edit by asking. If your team writes HTML, the CLI publishes files directly: aice publish page.html.
No. Anything that speaks MCP can publish — Claude, your editor's agent, a CI job. The connector and CLI are the only integration points.
Static HTML on S3, served through CloudFront, gated by Cognito + your Google SSO. No database. Your pages are files; you can list them, download them, and leave with them.
Pricing is announced at launch. Expect it to be flat, per-org, and boring — the infrastructure is static files, and the price will act like it.
First tenants are onboarded in order. We'll email when your slug is ready.
Expect exactly one email: the one that says your slug is ready. In the meantime, the product will remain boring.