# Sophia Stack X Every page of this site as Markdown. Each page also has its own copy at
/index.md. --- # Sophia Stack X Source: https://sophiastack.sophiaxt.com/ # The whole website platform, _in one file._ One program runs your entire website: the CMS, the web server and the build system. Built for people and for AI agents. [Install](https://sophiastack.sophiaxt.com/install) [Try it now](https://demo.sophiastack.sophiaxt.com/demo/start) ![The Studio editor: layers on the left, the page on a grid canvas in the middle with a floating toolbar on the selected hero, and the hero's gradient background settings on the right.](https://sophiastack.sophiaxt.com/shots/builder.webp) Publish: **Plain files, one-click rollback** Agents: **MCP server built in** Server: **One program, one database** Start here ## Two ways in. Pick the one that sounds like you. Both run the same program. ### [Build a website](https://demo.sophiastack.sophiaxt.com/demo/start) For owners and small teams. Try a private bakery site in the live demo for an hour, pick a template, or download the program and have a working site in about two minutes. No code needed. Open the live demo ``` 1. Open the live demo, nothing to install 2. Edit a page, publish it, roll it back 3. Or install it on your own computer or server ``` ### [Build with AI](https://sophiastack.sophiaxt.com/docs/ai-agents) For developers and agents. Every copy runs an MCP server with 55 tools, a content API, and an SDK with an OpenAPI spec and TypeScript types. An agent works in drafts, previews and rollbacks, and every call is logged. Read the AI agent guide ``` **$** sophia mcp MCP server on stdio, 55 tools **$** sophia docs the whole system as one text reference ``` New in the Studio ## Design it like a studio, not a form. The editor is a dark canvas workspace. Every page sits on the canvas, every section has real design controls, and nothing you set can leave text unreadable. ### The whole site on one canvas Every page laid out as an artboard. Zoom out to see them all, click one to edit it, pan with the space bar. Undo and redo cover every change. ![The Studio canvas zoomed out: the home page as a large artboard with the pricing and how-it-works pages beside it.](https://sophiastack.sophiaxt.com/shots/tile-canvas.webp) ### A library of 25 sections Heroes, features, pricing, testimonials, calls to action, FAQ, stats, logos, contact, team and gallery. Drop one in and replace the placeholder text. ![The Add panel open on Sections: thumbnails of ready-made sections beside the page.](https://sophiastack.sophiaxt.com/shots/tile-sections.webp) ### Effects Solid, gradient or picture backgrounds, corner radius, soft or glow shadows, frosted glass, full-screen height, and wave or curve dividers that blend into the next section. ![The Effects tab with drawn previews for corners, shadows, borders, height and dividers.](https://sophiastack.sophiaxt.com/shots/tile-effects.webp) ### Motion Fade, rise, zoom or slide in as visitors scroll. Off for people who ask for less motion, and every word stays readable without scripts. ![The Motion tab with entrance animations and delays.](https://sophiastack.sophiaxt.com/shots/tile-motion.webp) ### Theme, live Colors, fonts, buttons and presets for the whole site, previewed on the page as you change them. ![The Theme panel with presets and color fields beside the page.](https://sophiastack.sophiaxt.com/shots/tile-theme.webp) ### [Nova, a new template](https://sophiastack.sophiaxt.com/templates) A dark space look: gradient headlines, glass cards, glowing buttons and a tilted frame for screenshots. Five color presets. See all templates ![The Nova template: a dark starry page with a large gradient headline and glowing buttons.](https://sophiastack.sophiaxt.com/templates/nova.webp) ## Questions a buyer asks **Can I build a site without writing code?** Yes. Pages are built from blocks in a visual builder with a live preview, and the look (colors, fonts, buttons) is set on a Design screen that blocks unreadable text. Booking, a newsletter, a shop and forms are switched on, not coded. See [templates](https://sophiastack.sophiaxt.com/templates) or try the [live demo](https://demo.sophiastack.sophiaxt.com/demo/start). **Can I move my WordPress site without breaking links?** The importer reads a WordPress export file, brings over pages, posts, pictures, menus, WooCommerce products and approved comments, and makes every old address answer with a 301 redirect to its new page. It does not bring plugin shortcodes, custom post types or your old theme. [The walkthrough](https://sophiastack.sophiaxt.com/docs/migrate-from-wordpress) lists what comes over and how to check the redirects before you switch. **Can I install templates and extensions?** Yes, from the [marketplace](https://sophiastack.sophiaxt.com/marketplace) in one click or with `sophia market-install`. Each package is reviewed by SOPHIA XT and checked against a signed catalog. Extension code runs in a sandbox with only the permissions it declares. **What happens when something goes wrong?** Publishing checks links first, the last ten versions are kept, and any of them goes live again in one click. Backups of the database, pictures and settings are one button or `sophia backup`. A program update that does not answer within 30 seconds puts the old version back by itself. **Why trust a new platform?** You should ask. This is version 0.1.0, made by SOPHIA XT LLC. What we can show is below: your site is plain files you can host anywhere, downloads are signed and checkable, the [changelog](https://sophiastack.sophiaxt.com/changelog) is dated, and [benchmarks](https://sophiastack.sophiaxt.com/benchmarks) were measured on one machine with the method written down. [Compare](https://sophiastack.sophiaxt.com/compare) it with WordPress, Joomla and Ghost before you decide. ## You own your site The [license](https://sophiastack.sophiaxt.com/license) says: "What you make with it is yours: your content, your data, and the extensions, templates and sites you build." And on what happens if Sophia Stack X stops: "Your sites are published as plain HTML files, and every page also has a Markdown copy. You can serve them with any web server, and your content sits in one SQLite database file you control." Plain terms: the published site is ordinary files, so it keeps working on any web server. The program itself is not open source, so without it you would lose the admin and updates, but not your content or your pages. ## Your AI agent can build the site. Every copy runs an MCP server. Connect any MCP client and it works the way you do: drafts first, a preview, a check of what will change, then publish. If something is wrong, one call puts the last version back. * Creates and edits pages as drafts * Previews every page before it goes live * Shows what a publish will change, then publishes * Rolls back in one call * Every call lands in the audit log ``` # agent: add a pricing page and publish it $ entry_save {"site": "main", "collection": "page", "title": "Pricing"} saved entry 18 as a draft $ page_preview {"site": "main", "path": "/pricing"} status 200, no errors $ publish_preview {"site": "main"} 1 page added, 0 changed, 0 removed $ publish {"site": "main"} release 17 is live $ rollback {"site": "main", "release_id": 16} release 16 is live again ``` program to install: 1 database file: 1 tools for AI agents: 55 PHP, MySQL or Node to patch: 0 * Studio canvas * 25 ready-made sections * Section effects * Scroll motion * Undo and redo * Nova template * Page builder * Online booking * AI assistant * Newsletter * Visitor stats, no cookies * Articles * Shop * Stripe checkout * Discount codes * Forms * Events * Comments * Site accounts * Email * SEO audit * llms.txt * Markdown copies * MCP server ## Ready for local businesses. The apps a salon, clinic, contractor, shop or restaurant needs come with every copy. Switch one on and it fits the template you already use. * Online booking with opening hours, capacity and cancel links * An AI assistant that answers from your own pages, with your own API key * A newsletter with confirm-by-email and one-click unsubscribe * Pricing, team, reviews, opening hours, contact and before-and-after blocks * Visitor stats without cookies, and email set up in a minute ``` # agent: set up online booking for the salon $ extension_enable {"site": "main", "name": "bookings"} bookings is on $ entry_save {"site": "main", "collection": "service", "title": "Haircut"} saved entry 31 as a draft $ publish {"site": "main"} release 18 is live ``` [Play video](https://sophiastack.sophiaxt.com/video/restaurant-inbox.mp4) 39 seconds: restaurant menus, order and booking links, search, and the inbox. The restaurant in it is a made-up sample. ## Built with Sophia Stack X. A business that runs on it today, and the looks a new site can start from. ### [3 Point Forward](https://3pointforward.com) A Metro Detroit studio that builds and hosts websites for small businesses for $25 a week. Its site runs on Sophia Stack X. Visit 3pointforward.com ![The 3 Point Forward home page: Your website, built and hosted, for $25 a week, beside a laptop and phone showing a client site.](https://sophiastack.sophiaxt.com/showcase/3pf.webp) ### [Trade](https://sophiastack.sophiaxt.com/templates) For contractors, salons and clinics: a call button in the header, a call bar on phones and a quote form. See all templates ![The Trade template on a plumbing company's home page.](https://sophiastack.sophiaxt.com/templates/trade.webp) ### [A bakery you can edit](https://demo.sophiastack.sophiaxt.com/demo/start) The Hearth template with a shop, a cake inquiry form and four pages. Change it, publish it, roll it back. Try it now ![The Hearth bakery template home page.](https://sophiastack.sophiaxt.com/templates/hearth.webp) ### [Studio](https://sophiastack.sophiaxt.com/templates) Portfolios and agencies: big headlines and picture-led project cards. ![The Studio template home page.](https://sophiastack.sophiaxt.com/templates/studio.webp) ### [Journal](https://sophiastack.sophiaxt.com/templates) Writers and newsletters: serif reading text, drop caps and a signup panel. ![The Journal template blog list.](https://sophiastack.sophiaxt.com/templates/journal.webp) ### [Glass](https://sophiastack.sophiaxt.com/templates) Software and product sites. This site uses it. ![The Glass template: this site's home page.](https://sophiastack.sophiaxt.com/templates/glass.webp) ## Built in, not bolted on. Switch on what the site needs. No plugin store, no extra servers. ### Build pages from blocks Layers on the left, the real page in the middle at desktop, tablet or phone width, and every setting on the right. Agents can add the same sections over MCP. ![The Studio editor with layers, the page and the inspector.](https://sophiastack.sophiaxt.com/shots/builder.webp) ### Publish, then undo Publishing writes the site as plain files and checks every link first. Any earlier version goes back live in one click. ![The Publish screen listing versions, with the live one marked.](https://sophiastack.sophiaxt.com/shots/publish.webp) ### Design without code Colors, fonts and sizes with a live preview. Unreadable text is blocked before it saves. ![The Design screen with color fields and a preview.](https://sophiastack.sophiaxt.com/shots/design.webp) ### Sell from the same site Products, options, stock, discount codes, Stripe or pay later, emailed receipts, CSV export. ### Readable by AI search Every page also exists as Markdown. The site serves llms.txt and answers Accept: text/markdown. ``` **$** curl -H 'Accept: text/markdown' https://your-site.com/pricing # Pricing Three plans, billed monthly... ``` ## The real admin. Screenshots of the demo site. Click through it yourself in the live demo. ### Where the site stands What is live, what is waiting to publish, and who changed what. ![The dashboard: pages online, changes waiting, next steps and recent activity.](https://sophiastack.sophiaxt.com/shots/dashboard.webp) ### Pages from blocks Layers, a canvas with zoom, a floating toolbar on the selected section, and an inspector for content, design, effects and motion. Undo and redo cover every change. ![The Studio editor.](https://sophiastack.sophiaxt.com/shots/builder.webp) ### Every page at once The whole site as live thumbnails, drawn by its own template, with each page's state and address. ![The Canvas screen with every page as a thumbnail.](https://sophiastack.sophiaxt.com/shots/canvas.webp) ### Ready-made sections 25 designed sections with thumbnails. Pick one and it lands on the page with its design. ![The section library open beside the zoomed-out canvas.](https://sophiastack.sophiaxt.com/shots/canvas-all.webp) ### The look, checked Every color and size the template allows, tested for contrast, previewed at three widths. ![The Design screen.](https://sophiastack.sophiaxt.com/shots/design.webp) ### Versions you can return to The last ten versions are kept. The live site is plain files, so it stays up even if the admin is down. ![The Publish screen.](https://sophiastack.sophiaxt.com/shots/publish.webp) ### Bring your old site WordPress and WooCommerce, Joomla, or a folder of Markdown. Old addresses redirect. ![The Import screen.](https://sophiastack.sophiaxt.com/shots/import.webp) ### Your sign-in Two-factor codes, recovery codes, and every signed-in device with a sign-out button. ![The security screen with two-factor sign-in and signed-in devices.](https://sophiastack.sophiaxt.com/shots/security.webp) ## Secure before you touch a setting. Written from scratch in Rust by SOPHIA XT, not a fork of another CMS. On a server it runs as its own user in a locked-down service. Extensions run in a sandbox and get only the permissions they declare. * Two-factor sign-in and recovery codes * Ed25519-signed packages and updates * A one-time setup link, so nobody else can claim a new install * An audit log of every sign-in and change * Backups and restore built in * Scripts only from the site itself, by content policy ![The audit log listing publishes, rollbacks and uploads with who did them and when.](https://sophiastack.sophiaxt.com/shots/audit.webp) ## To a server in one command. sophia deploy copies the program and your sites over ssh, sets up the service, the web server and HTTPS, and checks the new version answers. If it doesn't, the old one comes back. * Signed updates: sophia update --latest * Three versions and three database copies kept * nginx, Caddy, or your own proxy ``` $ sophia deploy root@your-server --domain example.com --tls-email you@example.com sending the program (12 MB) unpacked version 20261110-235731 database copied to backups/pre-update-20261110-235731.db version 20261110-235731 is answering on 127.0.0.1:8806 site answers on example.com https://example.com is answering from here ``` ## Build on it. An extension is a folder: a manifest, templates and sandboxed JavaScript. The program checks, builds and signs it. ### Start from a working extension An app, block, component or template, ready to open. ``` **$** sophia new app tickets **$** sophia check extensions/tickets --json "ok": true ``` ### Permissions you can read server.js reaches only what its manifest declares. ``` // extension.json "permissions": ["data", "mail"] // server.js sx.data.create("ticket", { subject, email }) ``` ### A content API Entries, menus and media, with tokens limited to the scopes you grant. ``` **$** curl -H 'Authorization: Bearer …' \ https://your-site.com/api/v1/content/page 200 OK ``` ## Install it in _one line._ Linux server with systemd, as root. It checks the download, installs a locked-down service, sets up HTTPS and prints your setup link. Want to read the script first? The install guide shows how to download it, check its signature and then run it. `curl -fsSL https://sophiastack.sophiaxt.com/download/install.sh | sudo sh -s -- --domain example.com --tls-email you@example.com`Copy [Install guide](https://sophiastack.sophiaxt.com/install) [Try it now](https://demo.sophiastack.sophiaxt.com/demo/start) Free for any site, including client work, under the [SOPHIA XT license](https://sophiastack.sophiaxt.com/license). Also: [compare it with WordPress, Joomla and Ghost](https://sophiastack.sophiaxt.com/compare), [benchmarks](https://sophiastack.sophiaxt.com/benchmarks), the [changelog](https://sophiastack.sophiaxt.com/changelog). Downloads for Windows, Linux (Intel and ARM) and Apple-silicon Macs are on [Install](https://sophiastack.sophiaxt.com/install). --- # A CMS that AI agents can run over MCP | Sophia Stack X Source: https://sophiastack.sophiaxt.com/ai-cms # A CMS that AI agents can run over MCP # A CMS that AI agents can run over MCP Many CMSs let an AI write text into a box. Sophia Stack X lets an agent do the job the way an editor does: create a page as a draft, preview it, check what a publish would change, publish, and undo it. The agent connects through MCP, the Model Context Protocol, to a server that is part of the program. There is nothing extra to install. ## Connect an agent Locally, on the computer where the install lives: ``` sophia mcp ``` This runs an MCP server over standard input and output. Point your assistant's MCP settings at that command, run from the install's folder. In Claude Code, for example, add it to the project's `.mcp.json`. Remotely, an agent can call `POST /api/v1/mcp` with a bearer token. A site admin makes the token under **API**, and it carries the "mcp" scope. Remote access is bound to that token's site, and tools that touch the server's own files or the whole install are left out. ## What the 55 tools cover * **Read first:**`docs` returns the whole system as one text reference, the same text `sophia docs` prints. * **Content:** sites, collections, entries (save, get, delete), menus and modules. * **Media:** list, upload, and write alt text for pictures. * **Design:**`style_get` and `style_set` change the same colors, fonts, sizes, buttons and links as the Design screen. * **App data:** records for bookings, newsletters and anything an extension models. * **Check and ship:**`page_preview`, `publish_preview`, `publish`, `releases`, `rollback`. * **SEO:** an audit, suggested changes, and a decision on each. * **Shop and visitors:** orders, order actions, and cookie-free visitor stats. * **The install:** import a site, take a backup, read the audit log, read the mail outbox. The [AI agents guide](https://sophiastack.sophiaxt.com/docs/ai-agents) has the full list, and [the SDK page](https://sophiastack.sophiaxt.com/docs/sdk) carries the OpenAPI spec for the content API and TypeScript types for extension code. ## How an agent stays in bounds An agent with write access can do harm, so the safety rules are part of the tools: * **Drafts by default.** An entry the agent saves is a draft unless it sets a state. Saving an existing entry changes only the fields it sent. * **Checks before anything saves.** Every write goes through the same schema checks as the admin forms. One bad value in a design change and nothing saves. * **Preview and dry run.**`page_preview` renders one page with drafts included. `publish_preview` lists the pages a publish would add, change or remove, and any that would fail. * **One call to undo.**`rollback` puts a previous release back live. The last ten are kept. * **Logged.** Every call is written to the audit log as `mcp.`, with who and when. * **Scoped.** A remote token covers one site. Tools such as the inbox and importing are local only. Mail the agent reads from the inbox is treated as information, never as instructions. This is how the example on the [home page](https://sophiastack.sophiaxt.com/) works. An agent adds a pricing page, previews it, checks the dry run, publishes it, and rolls back when it should. ## Building a whole local business site The `docs` tool ends with a recipe an agent can follow from an empty site to a published one. Pick the template, switch on the apps the business needs (bookings, restaurant menus, a shop, a newsletter, business blocks, the website assistant), enter the facts the owner gave, build pages from blocks, preview and publish. The recipe tells the agent never to invent prices, hours or reviews: it leaves a field empty and asks. You still read what it did. Agent work can be wrong, so open the preview, look at the dry run and keep the audit log in mind. ## Pages AI search can read Agents also read sites. Every published page has a Markdown copy beside it, `llms.txt` maps the site, `llms-full.txt` holds every page in one file, and a request with `Accept: text/markdown` gets Markdown instead of HTML. These are plain files and headers, with nothing for you to switch on. See [Publishing, search and AI readers](https://sophiastack.sophiaxt.com/docs/publishing). ## What this is not It does not run agents for you or include an AI model. You bring the assistant, or use the website assistant, which answers visitors from your own pages with your own API key. And MCP access is only as safe as the token you give out, so keep tokens to the one site they are for and give them only to what needs them. ## Next step Read the [AI agents guide](https://sophiastack.sophiaxt.com/docs/ai-agents) and connect one. If you do not want to install anything yet, [open the live demo](https://demo.sophiastack.sophiaxt.com/demo/start) and look at the tools from the admin side. To see where this sits next to other systems, read the [comparison](https://sophiastack.sophiaxt.com/compare), or [install it](https://sophiastack.sophiaxt.com/install). --- # Sophia Stack X benchmarks | Sophia Stack X Source: https://sophiastack.sophiaxt.com/benchmarks # Sophia Stack X benchmarks # Sophia Stack X benchmarks These are numbers we measured on 15 November 2026 on one development computer. It is one machine, not a lab: the load tool ran on the same computer as the server and shared its CPU, nothing was tuned, and a different machine will give different results. We did not measure WordPress, Joomla or Ghost, so there are no comparisons here. Use the numbers to get a feel for the size of the program, not as a promise. ## The machine and the setup * Windows 10 Pro, AMD Ryzen 7 1800X (8 cores, 16 threads), about 80 GB of RAM, Samsung 970 EVO Plus NVMe drive. * Program: the Windows release build of version 0.1.0 (Rust, optimized, thin LTO, stripped), 32,214,528 bytes. * Data: a copy of the site you are reading, 24 pages and about 130 MB of site files including downloads, in a data folder of its own. * Server on `127.0.0.1:8874`, one process, no reverse proxy, no HTTPS, default settings. * Load tool: a small Python script using asyncio and raw keep-alive HTTP/1.1 connections, run on the same computer. A script like this can be the slowest part of the test, so treat the published-page throughput as a floor for the server, not a ceiling. ## Results | What | Result | | --- | --- | | Program size | 30.\. MiB (32,214,528 bytes), one file, nothing else to install | | Cold start to first answer | 521 ms median of 7 starts (range 516 to 577 ms), measured from launching the process to the first `200` for a published page | | Idle memory | 13.\. MiB working set, 10 seconds after start, before any request | | Memory under load | 24 MiB peak working set with 32 connections on a published page, 28 MiB peak with 32 connections on the preview | | Published page, 1 connection | 540 requests per second, p50 1.8 ms, p99 3.6 ms | | Published page, 32 connections | 3,984 requests per second, p50 5.1 ms, p99 54 ms, no errors in 39,942 requests | | Dynamic preview, 1 connection | 156 requests per second, p50 6.1 ms, p99 10.7 ms | | Dynamic preview, 32 connections | 177 requests per second, p50 165 ms, p99 427 ms, no errors in 1,804 requests | | Publish the docs site (24 pages) | 6.\. to 7.5 seconds, median 6.9 s, 5 runs | Each load run lasted 10 seconds, over the same page, `/docs/concepts`. ## What the numbers mean The **published page** is the path visitors normally use. It is a plain file served from a release folder, so one process answered several thousand requests a second with a few megabytes of extra memory. The p99 at 32 connections is probably the load script's own scheduling, since both ran on the same CPU. The **dynamic preview** is the admin's page preview. It renders the page through the template on each request with drafts included, behind a signed-in session. It is meant for one editor, not for visitors, and the numbers show it. It is far slower than the published page because it does the work that publishing does once. **Cold start** is the whole time from launching the process to the first answer. **Publish time** is the whole command, started from a new process, and it includes rendering every route, checking links, picture descriptions and placeholder text, and writing a new numbered release. The release for this site was about 8 MB on disk. The preview run signed in through the install's one-click demo mode, so the session check had that extra middleware in its path. ## How to reproduce 1. Download the program from [Install](https://sophiastack.sophiaxt.com/install) and [verify it](https://sophiastack.sophiaxt.com/verify). 2. Copy a data folder to a scratch place. Use `sophia backup` or copy it while the program is stopped. 3. Time a cold start: launch `sophia serve --data --bind 127.0.0.1:8874` and poll a page until it answers `200`. 4. Time a publish: `sophia --data publish ` several times, taking the median. 5. For load, use any HTTP load tool you trust on a page of your own site, and send the site's host name in the `Host` header. Run it long enough to see steady numbers, and say what the tool and the machine were. Read memory from Task Manager or `ps`. Run it on your own hardware and on the server you plan to use. If you get very different numbers, we want to hear about it. Back to [Compare](https://sophiastack.sophiaxt.com/compare), the [changelog](https://sophiastack.sophiaxt.com/changelog), or [install it](https://sophiastack.sophiaxt.com/install). --- # Blog | Sophia Stack X Source: https://sophiastack.sophiaxt.com/blog # Blog [November 11, 2026 · SOPHIA XT ## Introducing Sophia Stack X A CMS, web server and build system in one program, with an MCP server built in so AI agents can build and run sites the careful way: draft, preview, publish, roll back. Read more](https://sophiastack.sophiaxt.com/blog/introducing-sophia-stack-x) --- # Introducing Sophia Stack X | Sophia Stack X Source: https://sophiastack.sophiaxt.com/blog/introducing-sophia-stack-x November 11, 2026 · By SOPHIA XT # Introducing Sophia Stack X A CMS, web server and build system in one program, with an MCP server built in so AI agents can build and run sites the careful way: draft, preview, publish, roll back. Running a WordPress site means running PHP, a MySQL server, a stack of plugins and a steady stream of updates for all three. We wanted the site without the upkeep, so we built Sophia Stack X: one program and one database file that hold the CMS, the web server and the build system. ## What you get A page builder with a live preview at desktop, tablet and phone widths. Articles with this RSS feed, events, forms and moderated comments. A shop with options, stock, discount codes and Stripe checkout. Visitor accounts and email. Several sites and languages from one install. Importers for WordPress (with WooCommerce and comments) and Joomla, with old addresses redirected. Publishing writes the site as plain files and checks every link first. The last ten versions are kept, and any of them goes back live in one click. Because the live site is plain files, it stays up even if the admin is down. ## Built for AI agents Every copy runs an MCP server with 50 tools. An agent connected to it works the way a careful person does: it saves a draft, previews the page, checks what a publish will change, publishes, and rolls back in one call if something is wrong. Every call is written to the audit log. Sites built with it are easy for AI to read, too. Every page has a Markdown copy, the site serves llms.txt and llms-full.txt, and a request that asks for text/markdown gets the Markdown. ## Secure from the start It is written from scratch in Rust, not forked from another CMS. On a server it runs as its own user in a locked-down service. Sign-in has two-factor codes and recovery codes. Updates and extension packages are signed, and the installer checks every download against the signed release list before it runs anything. A new install only accepts its owner through a one-time setup link. ## Try it Click around the [read-only demo](https://demo.sophiastack.sophiaxt.com/admin), or [install it](https://sophiastack.sophiaxt.com/install) in three steps: download one file, open it, fill in one setup page. It runs on Windows, Linux (Intel and ARM) and Apple-silicon Macs, and it is free for any site, including paid client work. Follow along here, or subscribe to [the feed](https://sophiastack.sophiaxt.com/feed.xml) in any RSS reader. * release * announcement --- # Changelog | Sophia Stack X Source: https://sophiastack.sophiaxt.com/changelog # Changelog # Changelog What shipped, newest first. The current version is **0.1.0**. Updates are signed: on a server, `sophia update --latest` checks the release list against the SOPHIA XT release key before it changes anything. See [Install](https://sophiastack.sophiaxt.com/install). ## Next release ### 2026-11-15, not shipped yet * **Section design.** Backgrounds (solid, gradient, image), spacing, width, visibility per block, and a page canvas overview. These are builder controls being built now and are not in the current download. ## Version 0.1.0 ### 2026-11-12 * **Business apps.** Bookings with opening hours, capacity and cancel links. A newsletter with confirm-by-email and one-click unsubscribe. Business blocks: pricing, team, reviews, opening hours, contact and before-and-after. A website assistant that answers from your own pages, using your own AI key. * **Visitor stats without cookies.** * **Email.** Provider presets for setting up mail, an IMAP inbox, and List-Unsubscribe headers. * **Restaurant app.** Menus with dietary filters, locations, order and booking links, and Restaurant schema for search engines. * **Entry picker** for item fields, to link one entry to another. * **Video block** for video files kept on the site, with byte-range file serving so playback and seeking work. ### 2026-11-11 * **SEO and sharing.** SEO tools and social share cards (Open Graph and X). * **llms.txt** and Markdown copies of every page, for AI readers. * **RSS feeds** for dated entries. * **Extension and template marketplace** with a signed catalog. Every package is checked against it before it installs. * **Design tokens for buttons and links**, set on the Design screen and checked for contrast. * **Live demo workspaces.** A private bakery site, for an hour, that you can change, publish and roll back. * **Templates:** Trade, Studio and Journal. * **SDK.** An OpenAPI spec for the content API and `sophia.d.ts` TypeScript types for extension code. See [SDK](https://sophiastack.sophiaxt.com/docs/sdk). Version 0.1.0 also includes the earlier work: the page builder, publishing with rollback, WordPress and Joomla import, shop, forms, comments, accounts, two-step sign-in, backups, signed updates and the MCP server. ## Support policy Sophia Stack X is self-hosted, so you run it. That means: * **You run the server.** You install it, you keep the machine and its backups in order, and you choose when to update. SOPHIA XT does not host your site or have access to it. The program sends no content or data to SOPHIA XT and contacts the download site only when you ask it to check for an update. * **Updates are signed.** Every release is on a list signed with the SOPHIA XT release key, and `sophia update --latest` refuses anything that does not match. See [Verify a download](https://sophiastack.sophiaxt.com/verify). * **Security reports.** If you find a security problem, tell SOPHIA XT LLC privately through [sophiaxt.com](https://sophiaxt.com) before you publish it, with enough detail to reproduce it. SOPHIA XT LLC will look at it. * **No warranty.** The software comes without warranty, as the [license](https://sophiastack.sophiaxt.com/license) says. For other terms, such as a source review, contact SOPHIA XT LLC through sophiaxt.com. See also [Compare](https://sophiastack.sophiaxt.com/compare), [Benchmarks](https://sophiastack.sophiaxt.com/benchmarks) and the [license](https://sophiastack.sophiaxt.com/license). --- # Sophia Stack X compared with WordPress, Joomla and Ghost | Sophia Stack X Source: https://sophiastack.sophiaxt.com/compare # Sophia Stack X compared with WordPress, Joomla and Ghost # Sophia Stack X compared with WordPress, Joomla and Ghost WordPress, Joomla and Ghost are mature, widely used and free to run. Sophia Stack X is new (version 0.1.0). This page says where it works differently and where the others are the better choice. It sticks to design differences we can state from each project's own documentation. It has no speed or market-share claims about other products, because we did not measure them. If you spot an error, tell us and we will fix it. ## What you install | | Sophia Stack X | WordPress | Joomla | Ghost | | --- | --- | --- | --- | --- | | Written in | Rust | PHP | PHP | Node.js | | Runs on | One program file | PHP with a web server | PHP with a web server | Node.js with a web server | | Database | One SQLite file, made for you | MySQL or MariaDB | MySQL, MariaDB or PostgreSQL | MySQL in production | | Install | Open the file, or one command on a Linux server | Packaged by most hosts, or a manual install | Packaged by many hosts, or a manual install | Ghost(Pro) hosting, or the Ghost CLI on a server | | Source | Not open source. Free to use, including client work | Open source (GPL) | Open source (GPL) | Open source (MIT) | Open source is a real advantage for the other three: you can read the code, fork it, and the project does not depend on one company. Sophia Stack X's license lets you use it for free and keep everything you make, but you cannot read or fork the program. See [the license](https://sophiastack.sophiaxt.com/license). ## Plugins and extensions WordPress and Joomla add features through plugins or extensions, and each has a large public directory. A WordPress or Joomla plugin is PHP code that runs inside the same application as the rest of the site, so a plugin can do anything the site can. Sophia Stack X extensions are a folder with a manifest, templates and JavaScript. The JavaScript runs in a sandbox and can reach only the permissions the manifest declares, such as data or mail. Packages are signed, and the [marketplace](https://sophiastack.sophiaxt.com/marketplace) catalog is signed too, so a package changed on the way is refused. The cost of this design is size: every listing is reviewed by SOPHIA XT, so the marketplace has far fewer items than the WordPress or Joomla directories. Ghost has integrations and a themes marketplace, and offers a Content API and an Admin API. ## Updates Sophia Stack X updates with `sophia update --latest`. It checks the release list against an Ed25519 key built into the program, checks the file hash, copies the database, switches versions, and puts the old version back if the new one does not answer within 30 seconds. See [Install](https://sophiastack.sophiaxt.com/install). For the others, see their own update documentation. WordPress, Joomla and Ghost each have their own routine for core, plugin or theme updates, and the effort depends on your host. ## Static publishing Sophia Stack X publishes each site as plain HTML files in a numbered release, checks links first, keeps the last ten, and can put any of them back live in one click. Visitors get those files by default, and the files keep working on any web server. The admin is a separate part of the program. WordPress, Joomla and Ghost render pages from a database when visited, with caching on top, unless you add a tool that exports a static copy. This is a difference in design, not a verdict: a rendered-on-request site can do things a published folder cannot, such as per-visitor pages everywhere. Sophia Stack X handles forms, comments, shop checkout and accounts through its own routes next to the published files. ## AI agent access Sophia Stack X has an MCP server built into the program, with 55 tools for pages, design, media, publishing, rollback, SEO checks, orders and more. An agent works in drafts, previews a page, sees a dry run of a publish, and can roll back. Every call lands in the audit log. See [AI agents](https://sophiastack.sophiaxt.com/docs/ai-agents) and [a CMS AI agents can run](https://sophiastack.sophiaxt.com/ai-cms). We did not audit what AI integrations the other three offer through their own plugins, add-ons or hosted services. They change quickly, so check their documentation for the current state. ## Moving between them Sophia Stack X imports WordPress (with WooCommerce and comments), Joomla and Markdown folders, and keeps old addresses working with 301 redirects. The [WordPress migration walkthrough](https://sophiastack.sophiaxt.com/docs/migrate-from-wordpress) shows what comes over and what does not. Moving out is simpler than most: published sites are plain HTML with a Markdown copy of every page, and the content is in one SQLite database file. ## When to choose another one * You need a particular plugin or theme that exists for WordPress or Joomla and has no equivalent here. The ecosystem is where they are strongest. * You need open-source code you can read, fork or audit yourself. * You want a large community, many agencies and hosts who know the product, and years of track record. * You publish newsletters and memberships and want Ghost's focus on them. Sophia Stack X has a newsletter with confirm-by-email and a shop, but it is a general site platform, not a publishing product. * You want a hosted service run by someone else. Sophia Stack X is self-hosted: you run it. See the support section on the [changelog](https://sophiastack.sophiaxt.com/changelog). ## When Sophia Stack X fits * You want a single file to run, one database file to back up, and no PHP or Node stack to patch. * You want the live site to be plain files, with the admin kept apart. * You want AI agents to do real work on the site with drafts, previews and rollback instead of a free-for-all. * You build sites for small businesses and want bookings, a newsletter, a shop and an assistant that answers from your own pages included. Try it without installing anything in the [live demo](https://demo.sophiastack.sophiaxt.com/demo/start), or look at the [benchmarks](https://sophiastack.sophiaxt.com/benchmarks) we measured on one machine. --- # Documentation | Sophia Stack X Source: https://sophiastack.sophiaxt.com/docs Docs * [Overview](https://sophiastack.sophiaxt.com/docs) * [Quick start](https://sophiastack.sophiaxt.com/docs/quick-start) * [Concepts](https://sophiastack.sophiaxt.com/docs/concepts) * [Publishing and SEO](https://sophiastack.sophiaxt.com/docs/publishing) * [Importing](https://sophiastack.sophiaxt.com/docs/import) * [Shop](https://sophiastack.sophiaxt.com/docs/shop) * [Migrate from WordPress](https://sophiastack.sophiaxt.com/docs/migrate-from-wordpress) * [Forms, events and comments](https://sophiastack.sophiaxt.com/docs/forms-events-comments) * [Site accounts and email](https://sophiastack.sophiaxt.com/docs/accounts-email) * [Security](https://sophiastack.sophiaxt.com/docs/security) * [Extensions](https://sophiastack.sophiaxt.com/docs/extensions) * [AI agents](https://sophiastack.sophiaxt.com/docs/ai-agents) * [Content API](https://sophiastack.sophiaxt.com/docs/content-api) * [Deploying](https://sophiastack.sophiaxt.com/docs/deploy) * [Commands](https://sophiastack.sophiaxt.com/docs/commands) * [SDK](https://sophiastack.sophiaxt.com/docs/sdk) * [Business apps](https://sophiastack.sophiaxt.com/docs/business) # Documentation Prefer one file? Download [the whole manual as a PDF](https://sophiastack.sophiaxt.com/pdf/Sophia-Stack-X-Manual.pdf) or [the two-page overview](https://sophiastack.sophiaxt.com/pdf/Sophia-Stack-X-Overview.pdf). AI agents can read every page at once in [llms-full.txt](https://sophiastack.sophiaxt.com/llms-full.txt). ## Using it * [Quick start](https://sophiastack.sophiaxt.com/docs/quick-start): from a fresh install to a published site. * [How a site is put together](https://sophiastack.sophiaxt.com/docs/concepts): pages, blocks, collections, menus, modules, templates and publishing. * [Publishing, search and AI readers](https://sophiastack.sophiaxt.com/docs/publishing): releases, rollback, SEO, `llms.txt` and Markdown copies. * [Moving a site in](https://sophiastack.sophiaxt.com/docs/import): WordPress, Joomla, Sophia Stack 2 and Markdown folders. * [Shop](https://sophiastack.sophiaxt.com/docs/shop): products, options, discount codes, Stripe and orders. * [Forms, events and comments](https://sophiastack.sophiaxt.com/docs/forms-events-comments) * [Site accounts and email](https://sophiastack.sophiaxt.com/docs/accounts-email) * [Security and backups](https://sophiastack.sophiaxt.com/docs/security) ## Building on it * [Building extensions](https://sophiastack.sophiaxt.com/docs/extensions): manifests, templates, `server.js`, data models, admin screens and live page regions. * [AI agents](https://sophiastack.sophiaxt.com/docs/ai-agents): MCP tools, remote access and the rules agents follow. * [Content API](https://sophiastack.sophiaxt.com/docs/content-api): read and write content from other apps. * [SDK and API reference](https://sophiastack.sophiaxt.com/docs/sdk): the OpenAPI spec, TypeScript types for extension code, and the MCP tools. ## Running it * [Install](https://sophiastack.sophiaxt.com/install) * [Deploying from your computer](https://sophiastack.sophiaxt.com/docs/deploy) * [Command reference](https://sophiastack.sophiaxt.com/docs/commands) * [Full reference for agents and developers](https://sophiastack.sophiaxt.com/download/reference.txt), the same text `sophia docs` prints. --- # Site accounts and email | Sophia Stack X Source: https://sophiastack.sophiaxt.com/docs/accounts-email Docs * [Overview](https://sophiastack.sophiaxt.com/docs) * [Quick start](https://sophiastack.sophiaxt.com/docs/quick-start) * [Concepts](https://sophiastack.sophiaxt.com/docs/concepts) * [Publishing and SEO](https://sophiastack.sophiaxt.com/docs/publishing) * [Importing](https://sophiastack.sophiaxt.com/docs/import) * [Shop](https://sophiastack.sophiaxt.com/docs/shop) * [Migrate from WordPress](https://sophiastack.sophiaxt.com/docs/migrate-from-wordpress) * [Forms, events and comments](https://sophiastack.sophiaxt.com/docs/forms-events-comments) * [Site accounts and email](https://sophiastack.sophiaxt.com/docs/accounts-email) * [Security](https://sophiastack.sophiaxt.com/docs/security) * [Extensions](https://sophiastack.sophiaxt.com/docs/extensions) * [AI agents](https://sophiastack.sophiaxt.com/docs/ai-agents) * [Content API](https://sophiastack.sophiaxt.com/docs/content-api) * [Deploying](https://sophiastack.sophiaxt.com/docs/deploy) * [Commands](https://sophiastack.sophiaxt.com/docs/commands) * [SDK](https://sophiastack.sophiaxt.com/docs/sdk) * [Business apps](https://sophiastack.sophiaxt.com/docs/business) # Site accounts and email ## Site accounts Visitors can have accounts on your public site, separate from the people who edit it. Under **Site accounts** choose who can sign up (nobody, invited people, or anyone), which roles new accounts get, and whether they must confirm their email address: not at all, by a link that still lets them in, or before they can sign in. The pages are `/account/login`, `/account/signup`, `/account` for the profile, and `/account/forgot` for a reset. Reset links last an hour and replace any earlier ones. Confirmation links last three days. Both work once. Extensions can check a visitor's role, so you can build members-only pages and staff tools. Restyle the account pages by overriding them in your template. ## Email A super user sets the mail server under **This install > Email**: server, port, STARTTLS or TLS, username, password and the From address. Every message goes through one outbox, which retries six times and erases the message text once delivered. It keeps the subject and address for 30 days. Without a mail server, messages wait in the outbox, and a super user can open them there. That is how you follow reset links while testing. Links in emails use the site's public address, so a forged request cannot point a reset link elsewhere. --- # AI agents | Sophia Stack X Source: https://sophiastack.sophiaxt.com/docs/ai-agents Docs * [Overview](https://sophiastack.sophiaxt.com/docs) * [Quick start](https://sophiastack.sophiaxt.com/docs/quick-start) * [Concepts](https://sophiastack.sophiaxt.com/docs/concepts) * [Publishing and SEO](https://sophiastack.sophiaxt.com/docs/publishing) * [Importing](https://sophiastack.sophiaxt.com/docs/import) * [Shop](https://sophiastack.sophiaxt.com/docs/shop) * [Migrate from WordPress](https://sophiastack.sophiaxt.com/docs/migrate-from-wordpress) * [Forms, events and comments](https://sophiastack.sophiaxt.com/docs/forms-events-comments) * [Site accounts and email](https://sophiastack.sophiaxt.com/docs/accounts-email) * [Security](https://sophiastack.sophiaxt.com/docs/security) * [Extensions](https://sophiastack.sophiaxt.com/docs/extensions) * [AI agents](https://sophiastack.sophiaxt.com/docs/ai-agents) * [Content API](https://sophiastack.sophiaxt.com/docs/content-api) * [Deploying](https://sophiastack.sophiaxt.com/docs/deploy) * [Commands](https://sophiastack.sophiaxt.com/docs/commands) * [SDK](https://sophiastack.sophiaxt.com/docs/sdk) * [Business apps](https://sophiastack.sophiaxt.com/docs/business) # AI agents Sophia Stack X is built for AI assistants to work on as well as people. An agent learns the system from one plain text reference, then works through MCP tools that check every change like an admin form would. ## Connect an agent On the computer where the install lives: ``` sophia mcp ``` This runs an MCP server over standard input and output. Point your assistant's MCP settings at that command, run from the install's folder. In Claude Code, for example, add it to the project's `.mcp.json`. Remotely, an agent can use `POST /api/v1/mcp` with `Authorization: Bearer `. The token is a site API key with the "mcp" scope, made under **API** by a site admin. Remote access is bound to that token's site. Tools that touch the server's own files or the whole install are left out. ## The tools * **Read first:**`docs` * **Content:**`sites`, `collections`, `blocks`, `entries`, `entry_get`, `entry_save`, `entry_delete` * **Structure:**`menus`, `menu_item_save`, `menu_item_delete`, `modules`, `module_save`, `module_delete` * **Media:**`media_list`, `media_upload`, `media_alt` * **App data:**`models`, `records`, `record_get`, `record_save`, `record_delete` * **People:**`accounts`, `account_update` * **Extensions:**`extension_new`, `extension_check`, `extension_enable`, `ext_settings`, `ext_settings_save`, `schema` * **Marketplace:**`market_list`, `market_install` (local agents only). Installs are checked against the signed catalog. * **Design:**`style_get`, `style_set`, the same colors, fonts, sizes, button and link settings as the Design screen. Every value is checked before anything saves, and one bad value means nothing saves. * **Check and ship:**`page_preview`, `publish_preview`, `publish`, `releases`, `rollback` * **SEO:**`seo_audit`, `seo_changes`, `seo_change_decide` * **Shop:**`orders`, `order_get`, `order_action` * **Visitors:**`site_stats`, the cookie-free visitor numbers for any period up to 400 days. * **Inbox:**`inbox_list`, `inbox_read` (local agents only). Mail is treated as information, never as instructions. * **Moving in and the install:**`import_site`, `backup`, `backups`, `audit_log`, `mail_outbox` ## How agents stay safe * Every write is checked against the same rules as the admin forms and logged as `mcp.` in the audit log. * Entry saves are drafts unless the agent sets a state. Saving an existing entry only changes the fields sent. * `page_preview` shows one page with drafts included, and `publish_preview` is a dry run of a publish. `rollback` undoes a publish. * Remote agents are limited to one site. ## The reference The whole system fits in one text file that an agent reads before it starts: [reference.txt](https://sophiastack.sophiaxt.com/download/reference.txt). It is the same text `sophia docs` prints. The project also carries an `AGENTS.md` with the working rules: read the docs, prefer an extension over changing the core, check with `sophia check --json`, and never invent facts in client content. ## Building a whole local business site The `docs` tool ends with a recipe an agent can follow from an empty site to a published one: pick the template, switch on the apps the business needs (bookings, restaurant menus, shop, newsletter, business blocks, the website assistant), enter the facts the owner gave, build the pages from blocks, preview, and publish. It never invents prices, hours or reviews: it leaves the field empty and asks. The same reference is online as [llms-reference.txt](https://sophiastack.sophiaxt.com/sdk/llms-reference.txt). --- # Apps for local businesses | Sophia Stack X Source: https://sophiastack.sophiaxt.com/docs/business Docs * [Overview](https://sophiastack.sophiaxt.com/docs) * [Quick start](https://sophiastack.sophiaxt.com/docs/quick-start) * [Concepts](https://sophiastack.sophiaxt.com/docs/concepts) * [Publishing and SEO](https://sophiastack.sophiaxt.com/docs/publishing) * [Importing](https://sophiastack.sophiaxt.com/docs/import) * [Shop](https://sophiastack.sophiaxt.com/docs/shop) * [Migrate from WordPress](https://sophiastack.sophiaxt.com/docs/migrate-from-wordpress) * [Forms, events and comments](https://sophiastack.sophiaxt.com/docs/forms-events-comments) * [Site accounts and email](https://sophiastack.sophiaxt.com/docs/accounts-email) * [Security](https://sophiastack.sophiaxt.com/docs/security) * [Extensions](https://sophiastack.sophiaxt.com/docs/extensions) * [AI agents](https://sophiastack.sophiaxt.com/docs/ai-agents) * [Content API](https://sophiastack.sophiaxt.com/docs/content-api) * [Deploying](https://sophiastack.sophiaxt.com/docs/deploy) * [Commands](https://sophiastack.sophiaxt.com/docs/commands) * [SDK](https://sophiastack.sophiaxt.com/docs/sdk) * [Business apps](https://sophiastack.sophiaxt.com/docs/business) # Apps for local businesses Everything here comes with every copy. Switch an app on for a site under **Extensions**, then set it up from its screen in the admin menu. ## Bookings Online appointments for salons, barbers, clinics, therapists, contractors and consultants. * **Services** with a length, a gap after each one, a price and a picture. Each gets its own page with a booking form, and a services page lists them all. * **Opening hours** per weekday, with breaks (two rows for one day), closed dates, how much notice you need, how far ahead people may book, and how many bookings can share a time when you have several chairs or staff. * **The booking form** block: pick a service, a day and a free time, then name, email, phone and notes. Free times are worked out live and checked again when the booking is saved, so a time can never be double-booked past its capacity, even when two people press Book at the same moment. It works with scripts off too. * **Confirm straight away, or review first.** Customers get an email with the details, an "Add to calendar" file and their own cancel link. You get an email for every new booking and cancellation. * **The Bookings screen** shows today and what's coming, grouped by day, with Confirm, Done, No-show and Cancel, and a CSV export. Times are the business's own clock time. Set "Hours ahead of UTC" so minimum notice and "today" are right where you are. ## Newsletter A mailing list you run yourself, done lawfully. * **The signup** block asks for an email (and a name if you want), shows your consent sentence, and answers in place. * **Confirm by email** is on by default: people click a link before they're on the list. It keeps typos and other people's addresses out, and many countries require it. * **Campaigns:** write one, send yourself a test, then send to everyone who confirmed. Each email carries the person's own one-click unsubscribe link and your mailing address, and the app refuses to send without an address. Large lists go out in hourly batches with a Continue button. * **One-click unsubscribe in mail apps.** Campaign emails carry List-Unsubscribe headers, so Gmail, Outlook and Apple Mail show their own Unsubscribe button next to your name. Gmail and Yahoo expect this from anyone sending to many people. * **The Subscribers screen** shows counts by status, search, and a CSV export of confirmed addresses. ## Restaurant menus and locations For restaurants, cafes, bars, bakeries and food trucks, with one location or twenty. [Play video](https://sophiastack.sophiaxt.com/video/restaurant-inbox.mp4) The restaurant app and the inbox in 39 seconds. The restaurant in it is a made-up sample. * **Menus you type in once.** Sections like Starters and Drinks, then dishes with a price written the way you say it ($12, 12 / 18, Market price), a line of description, dietary labels (vegetarian, vegan, gluten-free, dairy-free, nut-free, spicy), a photo, and Popular or New tags. Lunch, brunch, drinks and kids menus are separate menus. Already have a printed menu? Add its pictures or the PDF instead. * **Locations** with address, tap-to-call phone, opening hours (closing after midnight works), a photo, a note like "cash only", and the menus served there, picked from a list. * **Order, delivery and booking links.** Paste the address from Toast, DoorDash, Uber Eats, Grubhub, OpenTable, Resy, your gift card page or any other service. The button says what it does (Order online, Delivery, Book a table, Gift cards) and each location gets its own. * **Blocks:** the menu with section links and dietary filter buttons, featured dishes, a location picker that shows today's hours and the right buttons, big order and book buttons, all locations, current promotions, and links per location. * **Found in search.** Each location page tells search engines it is a restaurant (or cafe, bar, bakery) with its address, hours, cuisine, price range and menu, and each menu page lists dishes with prices. ## Business blocks Page builder blocks made for local business sites, styled to match every template: * **Pricing**: up to four plans side by side, one highlighted as the most popular. * **Team**: photos, names, roles and short bios. * **Reviews**: customer reviews with stars and an optional summary line you write yourself, linking to where the reviews live. It adds no review markup for search engines, because search engines treat a business's own review markup as spam. * **Opening hours**: a table with an "Open now" or "Closed, opens at" badge worked out in the visitor's browser. Split days and hours past midnight work. * **Contact card**: address, a tap-to-call number, email, and Get directions buttons for Google Maps and Apple Maps. No embedded map, so no outside scripts. * **Logo strip**, **before and after** (a divider you drag or move with the arrow keys), **service list** (a menu of services with prices) and **steps** ("how it works"). * **Announcement bar** and **phone call bar** modules: a dismissible message along the top, and Call and Book buttons fixed to the bottom of phone screens. ## Website assistant An AI assistant on your site that answers visitors from your own pages, services, products and opening hours, using your own API key from OpenAI, Anthropic, Google or OpenRouter. * **Pick a template:** Receptionist, Booking helper, FAQ, Lead catcher or Shop helper. Each comes with its own instructions, greeting and starter questions, and you can add your own instructions on top. Every template forbids inventing prices, hours, policies or promises, and giving medical, legal or financial advice. * **Hand-off to a person:** when it can't answer, it offers to take the visitor's name, email and question, saves them as a lead and emails you. * **Your key stays on your server.** It is never sent to the browser, written into a page or shown in an error. * **Limits you set:** messages per day for the whole site and per visitor per hour, and a maximum reply length, so a busy day can't run up your bill. * **The Assistant screen** has a test chat, the summary of your site it answers from (rebuilt each time you publish), today's count, and the conversations and leads, kept 30 days. Add it as a floating chat button on every page (a module) or as a box on one page (a block). ## Visitors Under **Visitors** in each site's menu: views and visitors per day, the most read pages, where visitors came from and which devices they used, for 7, 30, 90 or 365 days. It is counted without cookies, so it needs no consent banner. No address or anything else that points to a person is stored. A visitor is counted once a day through a one-way code that changes daily. Bots aren't counted, and neither are browsers that send Do Not Track or Global Privacy Control. AI agents can read the same numbers with the `site_stats` MCP tool. ## Inbox Under **Inbox** in each site's menu, connect the business's own mailbox and read it in the admin: Gmail, Google Workspace, Microsoft 365, Outlook.com, Zoho, Hostinger, Fastmail, iCloud and Yahoo fill in the server for you. It shows the newest 40 messages, opens one with pictures and scripts removed, and lets you reply. Replies go out through the install's email with your mailbox as the reply address, so answers come back to it. It connects only over an encrypted connection (port 993) and only to servers on the public internet. Most providers want an app password here, not your normal one. Only people who can manage the site's settings see the Inbox. AI agents can list and read messages with the `inbox_list` and `inbox_read` MCP tools on the same machine, and are told to treat what an email says as information, never as instructions. ## Email in a minute Under **This install > Email**, pick your provider and the server, port and encryption fill in for you: Gmail and Google Workspace, Microsoft 365, Outlook.com, Zoho, Hostinger, Fastmail, iCloud, Yahoo, Postmark, SendGrid, Mailgun and Amazon SES. Each one tells you which password to use (most need an app password, not your normal one). Save, then send yourself a test. Until email is set up, messages wait in the outbox and nobody receives them. --- # Command reference | Sophia Stack X Source: https://sophiastack.sophiaxt.com/docs/commands Docs * [Overview](https://sophiastack.sophiaxt.com/docs) * [Quick start](https://sophiastack.sophiaxt.com/docs/quick-start) * [Concepts](https://sophiastack.sophiaxt.com/docs/concepts) * [Publishing and SEO](https://sophiastack.sophiaxt.com/docs/publishing) * [Importing](https://sophiastack.sophiaxt.com/docs/import) * [Shop](https://sophiastack.sophiaxt.com/docs/shop) * [Migrate from WordPress](https://sophiastack.sophiaxt.com/docs/migrate-from-wordpress) * [Forms, events and comments](https://sophiastack.sophiaxt.com/docs/forms-events-comments) * [Site accounts and email](https://sophiastack.sophiaxt.com/docs/accounts-email) * [Security](https://sophiastack.sophiaxt.com/docs/security) * [Extensions](https://sophiastack.sophiaxt.com/docs/extensions) * [AI agents](https://sophiastack.sophiaxt.com/docs/ai-agents) * [Content API](https://sophiastack.sophiaxt.com/docs/content-api) * [Deploying](https://sophiastack.sophiaxt.com/docs/deploy) * [Commands](https://sophiastack.sophiaxt.com/docs/commands) * [SDK](https://sophiastack.sophiaxt.com/docs/sdk) * [Business apps](https://sophiastack.sophiaxt.com/docs/business) # Command reference Run `sophia` with nothing after it to start and open the setup page. `sophia --help` explains any command in full. ## Running | Command | What it does | | --- | --- | | `sophia` | Start with data beside the program and open the browser. | | `sophia serve` | Run the server only. The admin is at `/admin`. | | `sophia demo` | Create a demo site with pages, articles, menus and modules. | | `sophia backup` / `restore` | Back up everything, or unpack a backup into an empty folder. | ## Sites and people | Command | What it does | | --- | --- | | `site-create