Custom domains everywhere, stricter transport
- Custom domains on WHM/cPanel installations: a verified domain is now connected to the web server and gets its own HTTPS certificate automatically (via cPanel AutoSSL). The Domains page shows "Waiting for certificate" until it is in place, then "Active".
- HSTS is sent by the site and the API on HTTPS installations.
- Domains page: a "Check again" action for domains that are verified but not yet active, with the reason shown.
- Isolated apps on a single server: with the sandbox helper, every project builds and runs as its own system user inside a systemd scope with memory, CPU and task limits — tenants cannot read each other or the platform. This is what makes open sign-up safe on the process provider.
- Approval mode for sign-up (
FASTBASE_SIGNUP=approval): anyone can register and explore; an administrator approves the account with one click under Admin before it can deploy or provision resources. Administrators are emailed about new registrations, the person is emailed on approval; invited addresses and the first account skip the queue. - The site footer shows the operating company (
FASTBASE_COMPANY_NAME). - Connecting an agent is copy-and-paste: right after a token is created, Settings shows the ready-made command for Claude Code or Codex (wrapped for Windows PowerShell) or the JSON for Cursor, Windsurf and other editors — the token already filled in. The same panel sits on New project.
- Signed-in people are no longer sent back to the sign-in form from the public pages: the site header shows Dashboard, and the sign-in page skips itself when a session exists. Settings moved to the end of the sidebar with a gear icon.
- The agent does the mechanics:
fastbase_analyze_projectnow returns guidance (what to do first, the only values to ask the user for, what FASTBASE handles itself), the MCP server carries instructions for agents, and secrets an app signs its own data with (JWT_ACCESS_SECRET,MEDIA_SIGNING_SECRET, salts…) are generated automatically instead of being requested from the user. Monorepos deploy from the repository root with a Procfile. - Background workers: a
worker:line in a Procfile (or a worker command in the project's build settings) starts a second process next to the app — no port, same environment, restarted on crashes. Queue consumers and schedulers no longer have to live inside the web process. - For coding agents: the API root describes the service and how to connect,
/llms.txtexplains FASTBASE to agents, and the MCP server, CLI and SDK are published on npm asfastbase-mcp,fastbase-cliandfastbase-sdk(npx -y fastbase-mcp).