Qyverix Cloud
Hosting is easy to sell and hard to trust. The design question was not how to make deployment fast — it was how to make going back so cheap that shipping stops being frightening.
Challenge
Deployment platforms compete on how fast they ship. The expensive moment is the other one: a release goes wrong and the only way back is a rebuild and someone answering a ticket.
Approach
Make every earlier build restorable without rate limits, publish claims specific enough to be falsifiable, and state the platform's current limits on the marketing page rather than in a support reply.
Outcome
Live at cloud.qyverix.in with push-to-deploy from GitHub, two plans, isolated databases and a published list of what it does not do yet.
The brief
What the business needed.
Qyverix Cloud is the hosting underneath the studio's own client work, opened up so others can run on it — the same machines, the same deploys, the same people answering. Several of the sites in this portfolio serve from the infrastructure the product sells, which is the only endorsement worth printing.
The setup is three steps and then it is automatic: install the client on GitHub, pick a repository and branch — public or private — and every push to that branch builds and replaces what is running. Traffic moves once the new build answers, and the old one stays restorable. Rollback is re-deploying any earlier build, not rate limited, with commit, outcome and timing kept for every build in the history.
The part that took the most discipline was what the page refuses to claim. There is a section titled "What it does not do yet", and it says so plainly: SFTP with keys only and no file browser, nightly backups that are restored on request rather than downloaded, logs as a snapshot rather than a live tail, email support with no ticket system, GitHub only, and one region in India with no global edge network. Every figure in the pricing table is read from the same table that charges the card and enforces the entitlement, so the page cannot drift from the invoice.
What we built
Shipped scope.
Push to deploy
Connect a repository and a branch — private repositories included — and pushes deploy themselves, with full build history keeping commit, outcome and timing.
Rollback without limit
Re-deploy any earlier build, not rate limited. Traffic moves only once the new build answers, and the previous one stays restorable.
Isolated databases
Row-level security in Postgres, per tenant and per query, with MariaDB, PostgreSQL and MongoDB on Pro and remote access from DBeaver, TablePlus or your own code.
Certificates and teams
TLS certificates issued and renewed without asking, team members with scoped access, and session control showing active sessions with sign-out everywhere.
Falsifiable claims
A section of security claims specific enough to be wrong — tenant separation by transaction, the privileged process unreachable from customer traffic, read-only repository scope, sessions stored only as SHA-256 hashes.
Published limits
A standing list of what the platform does not do yet — file browser, downloadable backups, live log tail, ticketing, non-GitHub repositories, multi-region — stated on the page rather than discovered later.
Build details
How it was made.
- Stack
- GitHub app integration, containerised builds, Postgres with row-level security
- Scope
- Product, platform engineering, billing and entitlements, operations
- Sectors
- Developer tooling, hosting, agencies and studios
- Coverage
- One region, India
- Status
- Live — Student ₹50/mo, Pro ₹149/mo — cloud.qyverix.in ↗
FAQ
Questions this raises.
What happens when a deployment breaks the site?
You re-deploy an earlier build. Every build is kept with its commit, outcome and timing, rollback is not rate limited, and traffic only moves to a new build once it answers — so the previous one is always there to go back to.
What does Qyverix Cloud not do?
It is published on the page rather than hidden: SFTP with keys and no file browser, nightly backups restored on request but not downloadable, logs as a snapshot rather than a live tail, email support with no ticket system, GitHub only, and a single region in India with no global edge network.
More work