Deploy from your repository
Connect GitHub or GitLab once. We show exactly which permissions the connection needs before you authorise it, validate the token on entry, and store it in Vault — never in a database column and never in a log.
Hosting for developers
Hosting that behaves like a tool, not a control panel
Deploy from the GitHub or GitLab repository you already work in, branch a staging copy and push it live when it is ready, open real VS Code in the browser on the running site, and drive the whole platform from a REST API, a CLI and an MCP server. Everything the dashboard does, the API does — because the dashboard is built on it.
14-day free trial — card required, not charged
Read the API reference- 100%of the API documented at build time
- MITZinnector® CLI, free, no account to try it
- 12MCP tool categories for AI agents
- No lock-intake the code and go, whenever
- Git deploysfrom GitHub or GitLab, the repository you already use
- Staging and push-to-livea real copy, one click, then promote it
- VS Code in the browseron the live site's real files, git included
- A real public APIversioned, documented, and the one we build on
The workflow, not a screenshot of one
Four things that turn hosting from somewhere you upload files into somewhere you ship from.
Staging with push-to-live
Branch the whole site — files and database — work on the copy, then promote it. Test the thing you are about to ship on a copy of the thing you are shipping to.
VS Code in the browser
Real code-server on the live site's files, with git built in, inside the same CageFS-isolated jail your SFTP session lands in. Nothing to install, nothing to sync.
Your own tools, still
SFTP on every site, inside the same isolated jail as the browser editor. Use the browser editor for one task and your own client for the next — both see the same files.
Zinnector®, the CLI
Build WordPress locally with nothing installed but Node — no Docker, no MAMP — then check what you built against the platform it is going to. Free and MIT-licensed.
An MCP server for your agent
Twelve categories of real actions — sites, code, domains, DNS, SSL, databases, configuration, backups, email, SEO and observability — so an AI assistant can do the work rather than describe it.
Every door into the platform
The dashboard is one client of the API. These are the others, and they are all public.
REST API reference
Every operation, generated from the OpenAPI spec that is the source of truth — so the docs cannot drift from the endpoint.
REST API reference →The developer platform
How the API, SDKs, Terraform provider and webhooks fit together, and what to reach for when.
The developer platform →CLI command reference
Every Zinnector® command, generated from the tool itself rather than written beside it.
CLI command reference →Zinnector® — the CLI
Local WordPress on Node alone, and pre-flight checks against the platform you are deploying to.
Zinnector® — the CLI →Webhooks
Events pushed to you, signed and retried, so you do not poll us.
Webhooks →MCP tool catalogue
What an AI agent connected to your account can actually do, listed action by action.
MCP tool catalogue →The things that only matter once you are working
Small print that is not small when it is your Tuesday afternoon.
- Per-site PHP version, so one site can move to 8.4 without dragging the others with it
- Per-site cron and environment variables in the dashboard, not in a file you have to remember
- phpMyAdmin and a file manager for the times a GUI really is quicker
- SFTP into each site's isolated jail, with keys managed in the dashboard
- Free migrations, done and verified before anything is switched over
- Free SSL issued and renewed for you, on every site
- SFTP rather than an interactive shell on every site — the account is created with /sbin/nologin and SFTP enters the jail through PAM, which is a security decision rather than a missing feature
From repository to live site
The path a change takes, once the connection exists.
Connect the repository
Authorise GitHub or GitLab once, having seen the exact scopes first. The token is validated on entry and written to Vault.
Branch a staging copy
Files and database, one click. Your staging copy is the site, not an approximation of it.
Push, and we deploy
A push to the branch you nominated deploys to that environment. Static sites can go to our fleet, Cloudflare Pages or GitHub Pages, chosen per site.
Promote to live
When it is right on staging, push it live. Every deploy is a versioned release, so if it is wrong afterwards you roll back to the previous one rather than opening a restore ticket.
FAQ
Do I get SSH?
Not an interactive shell: accounts are created with /sbin/nologin and you get SFTP into the site's CageFS jail instead, alongside the browser IDE with git built in. We would rather tell you that here than have you find out after you have paid.
Is the public API the same one the dashboard uses?
Yes, and that is the point. It is API-first: no endpoint ships unless it is in the OpenAPI spec, and the SDKs, the CLI and the reference on this site are all generated from that spec. There is no private API with the good endpoints in it.
Which languages and stacks?
WordPress and WooCommerce, plain PHP, Laravel, Node, Python and Django, .NET, static sites and modern app frameworks. Or take an unmanaged machine with root and run whatever you like on it.
What is the MCP server for?
It lets an AI assistant — Claude, or anything else that speaks MCP — take real actions on your account instead of telling you which button to press. What it can do is listed in the tool catalogue, and you decide what it is allowed to touch.
Am I locked in?
No. Every site can be exported, the code is in your repository, and the platform is deliberately built with swappable providers underneath it. If you want to leave, the answer is a migration rather than an argument.
Can you build the thing as well as host it?
Yes — that is a separate service and a separate decision. Development is quoted per project, and hosting it with us is never a condition of it.
Support is included, and somebody is always there
Every plan comes with it. There is no support tier to buy, no per-incident charge and no ticket allowance — and the desk is open 24 hours a day.
Free on every plan
Support is part of hosting, not an upsell. It is the same support on the smallest plan as on the largest, and nothing about it is counted or capped per incident.
Open 24 hours a day
Whatever hour you are working and whatever time zone you are in, the desk is staffed. You are not writing into an inbox that opens in the morning.
Every one of our 58 languages
Write your ticket in the language you actually think in — we translate it for our team and answer you in yours, with the original always one click away. We sell in all 58.
A person, not a bot
Our assistant answers instantly from the knowledge base, but it never closes a ticket for you. A ticket is picked up and answered by somebody who can act on it.
Related
Build on it free, and pay when it is live
Start on the free trial, connect a repository and deploy something. If you would rather we built it for you, the development quote is free too.
Start free