Deploy Instatic
Design, write and publish your site on your own Instatic
Deploy Instatic, the open source visual CMS, with managed Postgres, a persistent volume for media and a public HTTPS URL. The owner account is created for you at deploy, so the site is yours from the first minute.
What you get with Instatic
- Visual editorBuild pages on a canvas with layers, classes and breakpoints side by side. Paste HTML and it becomes editable blocks.
- Clean published pagesPublishing writes plain HTML and CSS without the editor runtime. Visitors get a fast static page on your URL.
- Content and mediaWrite posts in the content workspace, keep images in the media library and let Instatic generate responsive image sizes.
- Users and rolesAdd editors, designers and developers with their own roles. Publishing asks for the password again before it replaces the live site.
- Owner set at deployInstatic opens a first run setup to whoever visits first. The template completes it on first start with a generated password.
- Optional AI assistantConnect your own Anthropic, OpenAI, OpenRouter or Ollama key to edit pages and content with the assistant. Keys are stored encrypted.
After you deploy Instatic
- 1Open /admin on the public URLThe hostname is on the app page after deploy. The first start runs the database migrations and sets up the owner account, usually in under a minute.
- 2Sign in as the ownerCopy INSTATIC_ADMIN_PASSWORD from the app’s Variables in the dashboard, sign in as admin@example.com, then change the email in your profile.
- 3Build the home page and publishOpen Site, add or paste content into the page, then press Publish. Your public URL serves the published pages.
How Instatic is wired
Instatic and Postgres ship together. The public hostname serves the published site, and the admin lives under /admin on the same host. Media and published files sit on a volume.
- Postgres holds the site
- Pages, posts, users, roles and settings live in the attached database. Restart or redeploy the app and everything is still there.
- Media on a volume
- Uploads, generated image sizes, fonts, plugin packages and published files live on a 5 GB volume mounted at /app/uploads.
- Keep the secret key
- INSTATIC_SECRET_KEY encrypts AI provider keys, plugin secrets and MFA seeds. It is generated once at deploy. Changing it makes them unreadable.
- One replica
- Live collaboration and render caches run inside the app process, so the template runs a single replica. Add CPU and memory from the dashboard as the site grows.
Why run Instatic on StackBlaze
- Scale your appChange CPU, RAM, and replicas without a rebuild, or let autoscaling add replicas when CPU climbs.
- Git-based CI/CDPush to GitHub and it builds and ships. Pull requests get their own preview URL on Pro and Business.
- One-click rollbackA deploy went wrong? Go back to any previous successful deploy.
- Environments built inProduction, staging, and dev as separate environments in one project, each with its own URL.
- Built-in observabilityCPU, memory, and response time per app, live logs with search, and alerts to Slack, Discord, or a webhook.
- Developer-first toolsA CLI and Stack MCP: deploy, read logs, and wire services from your terminal or your AI assistant.
- Built for teamsInvite teammates with roles. An audit log records who changed what.
- Managed Postgres with HAPostgres is run for you. Turn on high availability for a three-node cluster when the app needs it.
Common questions about Instatic
How do I sign in after deploy?
Open /admin on your public URL and sign in as admin@example.com. The password is generated at deploy and shown as INSTATIC_ADMIN_PASSWORD in the app’s Variables in the dashboard.
Can someone else claim my new site?
No. Instatic’s first run setup is open to the first visitor, so the template completes it itself on first start with your generated owner password. Any later setup request is refused.
Does Instatic send email?
No. Instatic has no email features. Add users from the Users page and set their passwords there. Form submissions are stored in your data tables.
Which database does it use?
PostgreSQL, created with the app. Instatic also supports SQLite, but the template uses Postgres so content is not kept in a file inside the container.
Do I need an AI key?
No. The editor works without one. The AI assistant is optional and uses your own provider key, saved encrypted in Instatic’s AI settings.
Can I use my own domain?
Yes. Attach a custom domain from the dashboard, then add it to PUBLIC_ORIGIN as a second, comma separated entry so the admin accepts requests from it. Custom domains
Is it ready for production?
Instatic is actively developed and still before version 1.0. The template pins a release; read the release notes before you move to a newer image tag.
What does it cost?
You pay for the compute, storage and bandwidth Instatic and Postgres use, not per page, per seat or per publish. Pricing
More CMS templates
WordPress CMSBuild and manage websites, blogs, and content experiences with the world's most popular CMS.
directusThe flexible backend for all your projects. Turn your database into a headless CMS, admin panels, or apps with a custom UI, instant REST and GraphQL APIs, auth and more.
strapiOpen-source headless CMS. Edit content in a clean admin panel and serve it to any frontend over REST and GraphQL, with a media library and role-based access.
payloadOpen-source TypeScript headless CMS and website builder on Next.js. Edit pages and posts in the Payload admin with live preview, drafts and scheduled publishing, and serve them on the built-in website or over REST and GraphQL.