zDeploy · part of the Zaytoun Network
zDeploy is where data sovereignty starts: push-button app hosting on infrastructure you can verify, today. Domain registration and infrastructure provisioning are next — hosting is the first rung, not the whole ladder.
New · zDeploy MCP
Connect zDeploy to your vibe-coding tool once, then keep Vibing. Describe what you want — it writes the code, provisions a database, and ships it to a live URL on ethical infrastructure. The simplest way to get your products deployed on tech that shares your values.
Activate Deploy and paste a single MCP URL into your vibe-coding tool (Cursor, Claude, and friends). Nothing else to configure.
“Build me a recipe site with a database.” It writes the app, adds the services it needs, and pushes the code — no git, no Docker, no YAML.
Your app comes up on your domain with HTTPS already issued — running on infrastructure chosen for its conscience, not its margins.
Vibe coding doesn't have to mean no version control or dodgy deployments. Every push lands in a real git repo you own. Every deploy is a versioned, professional release — automatic HTTPS, health-checked rollout, one-click rollback. The speed of just-keep-Vibing, with the discipline of real infrastructure underneath.
Every push is a commit in a private git repo that's yours — full history, no lock-in, take it anywhere.
Each deploy is a versioned release rolled out across a container swarm: automatic HTTPS, health checks, and one-click rollback if anything's off.
No tarball-to-a-VPS, no secrets in a chat log. Proper isolation, proper releases — the boring parts done right so you can keep Vibing.
The Wedge
You want your apps and data off Big Tech's infrastructure — but you shouldn't have to give up the push-button ease it trained you to expect. zDeploy keeps the convenience, and changes who owns the substrate underneath it.
Not Big Tech. Not funded by complicity. Your apps run on substrate you can verify, chosen for its values, not its margins.
About our infrastructure, honestly
During the beta our hosting substrate is transitional — we're mid-migration to providers we can verify are clean of Big-Tech complicity. We'd rather tell you that plainly than pretend we're already there. The migration is public, and your apps move with it at no cost to you.
Connect or upload, and you get a live URL with HTTPS in minutes. No DevOps, no YAML, no pager.
Custom domains, an optional Postgres database, full version history. You own all of it — no lock-in.
Honest pricing, stated plainly. No fake scarcity, no countdowns, no pre-checked upsells. Ever.
What's coming
zDeploy starts with hosting because it's the piece you need today. It doesn't end there — the plan is to give you a way off Big Tech at every layer of your stack, not just the one you're renting from us now.
Push-button deploys, custom domains, automatic HTTPS. Live today, running on infrastructure you can verify.
Register and manage domains through an ethical registrar — no Big-Tech middleman sitting between you and your own name on the internet.
One-click hardened clusters on EU-sovereign bare metal — for teams that want to own the machines, not just rent space on them.
Honest roadmap, not a promise with a date on it: domains and provisioning are planned, not live. We'll say so plainly here until they ship — no countdown, no "coming Q3."
Where we stand
Every app has to run on someone's machines, paid for by someone's money, governed by someone's rules. Most hosting hides those choices. We make ours legible — and where we can't yet meet our own bar, we say so rather than dress it up.
Your hosting fees don't fund a surveillance-advertising giant. They fund independent infrastructure and Zaytoun's cause pool. We name our providers and our advertiser relationships publicly — nothing routed through a company whose business model we're trying to end.
Still in progress: Mid-migration to providers we can verify are clean — the move is public, and your apps move with it at no cost.
Before we run your apps on a provider, we do the due diligence — and, to the best of it, we choose companies that are independent (no private equity, venture capital, or Big-Tech ownership pulling the strings), that power their machines from green energy, and that are not headquartered in, owned by, or operationally dependent on states credibly accused of genocide or systematic human-rights abuse. Infrastructure is a moral choice, and we make it deliberately.
Still in progress: Due diligence has limits, and we're honest about them: provider ownership and energy sourcing aren't always fully transparent. We publish our current providers and what we've been able to verify — and we move when we learn better.
Your app runs across a container swarm, not a single fragile box — replicas converge, failed containers are rescheduled, and certificates auto-renew. Resilience isn't a premium add-on; it's how the platform is built. The point of independent infrastructure is wasted if it can't keep your app online.
Still in progress: We're a young platform, so we won't quote a five-nines SLA we haven't earned. Our real uptime, incidents and all, will be published on the transparency page rather than promised in marketing.
Your code, your data, your domain, your full version history — all yours, all exportable. No proprietary lock-in, no formats you can't take elsewhere. The door out is as easy as the door in. An ethical host has to be one you're free to leave.
Honest prices stated plainly, no fake scarcity, no countdown timers, no pre-checked upsells, no "are you sure you want to cancel" guilt mazes. We will not optimise revenue by manipulating you. If we ever do, hold us to this paragraph.
Infrastructure is not neutral, and we won't pretend it is. We refuse apps built to surveil, deceive, harass, or strip people of their rights. We'd rather lose the customer than power the harm. The line is drawn on purpose, and we'll defend it in public.
Still in progress: Our acceptable-use line is being written into clear, published policy before the public beta.
This is the standard we hold ourselves to, in public. See the wider charter on why zDeploy exists and the numbers behind it on our transparency page.
How it works
A short, friendly form — no Docker knowledge required. Tell us what to run and where people should reach it.
We build or pull your app and roll it out across our container swarm. You watch it happen, live — not a dead spinner.
Your app comes up on your domain with a certificate already issued. Share the URL — it's real, and it's yours.
What you can deploy
Built assets, single-page apps, documentation, marketing sites. Fast to serve, simple to ship.
react · astro · hugo · plain html
Anything you can put in a container image. Bring a prebuilt image today; build-from-repo is coming.
ghcr.io/you/app:latest
Toggle on a managed PostgreSQL database and we wire it in automatically — your app just gets a DATABASE_URL.
postgres · wired automatically
Plans
Three tiers, stated by the resources you actually get. Deploy is free during the beta — no charges of any kind right now. The prices shown for Starter and Pro are our intended model, not a live charge. We will be clear before anything costs money. No card to start, no pre-checked add-ons.
Free during beta — and always for a first app
Planned — free during beta
Planned — free during beta
Deploy is free during the beta. No payments are taken right now. The prices shown are our planned model. When paid tiers open, the database, custom domain, and TLS will be included — not sold as add-ons. Storage will not be silently throttled; exact allowances and overage terms will be published before any charges apply. No per-seat fees. No surprises.
Ethical data sovereignty
Your apps deserve to run on infrastructure you can verify — not rent from Big Tech. No card required. Live in minutes.