A TANVRIT PRODUCT
Tanvrit Host
Beta
Push a build. Get a URL.
Static site hosting built ground-up and vendor-neutral. Deploy to an instant subdomain, promote dev → qa → uat → prod, and bring your own domain with automatic HTTPS. Deploys are content-addressed, so rollback is instant.
In beta. Ask us about access and what is available today.
AT A GLANCE
tanvrit host
Instant *.sites.tanvrit.com subdomain on every push
Promote dev → qa → uat → prod without rebuilding
Custom domains with automatic HTTPS
Content-addressed deploys — delta upload, atomic rollback
Pluggable storage; not locked to one cloud
Built for
- Web
- CLI
THE EVERYDAY DETAILS
Deploys that are pointers, not uploads
A deploy on Tanvrit Host is an immutable manifest plus content-hashed blobs. The client hashes every file, the control plane replies with only the blobs the site does not already have, and those go straight to object storage through presigned URLs. Finalising writes the manifest and flips one route pointer. Because nothing is ever mutated in place, rollback and promotion are the same operation as deploying: write a different deployment id to the route.
Four environments, one artifact
Every site has dev, qa, uat and prod, each an independent route pointer with its own host. Production answers on your site's subdomain, and the others use a double-dash prefix so a site literally named qa cannot collide with an environment name. Each deploy also gets an immutable preview host keyed by its deployment id. Promoting from uat to prod moves the exact artifact you already tested — no rebuild, no re-upload, so the bytes in production are the bytes you signed off on.
Serving is not tied to one vendor
Bytes are served by a Ktor origin you can run behind the API or standalone on a Linux node — the same code, a different storage environment. Every read goes through one StorageProvider interface, with implementations for object storage and the local filesystem, so changing backend is a configuration flip rather than a rewrite. No vendor edge runtime sits in the request path. The origin reads only from storage on the hot path, so hosted sites keep serving even when the control plane is unavailable.
Custom domains and certificates
HTTPS is issued by Caddy using on-demand ACME rather than a vendor SaaS certificate product. Before minting a certificate for an incoming hostname, Caddy calls an authorization endpoint on the origin, which returns success only for a managed subdomain or a customer domain that has passed DNS verification. That gate exists to protect the certificate authority rate limit: without it, any hostname pointed at the platform could trigger an issuance attempt and exhaust the quota for everyone.
A LITTLE CLARITY
Your questions, answered.
It is in private beta, not general availability. The console runs at host.tanvrit.com and the serving origin, deploy CLI and storage layer are in place, but the platform is still being brought up on production infrastructure. Treat availability as invite-based rather than self-serve.
As long as it takes to write one small object. The manifest and blobs for the older deployment were never deleted or modified, so a rollback rewrites the route pointer to that deployment id. There is no rebuild step and no re-upload.
Only the blobs whose content hash the site has not seen before. The CLI hashes the directory into a manifest, the server diffs it against existing blobs and returns presigned upload URLs for the missing ones, and the client PUTs those directly to storage. For a typical content change that is a handful of files, not the whole build.
Storage access is confined to a single provider interface with object-storage and local-filesystem implementations, and the request path contains no vendor-specific edge runtime. Adding a backend means writing one implementation; nothing else in the serving path changes. A plain CDN can sit in front as a pass-through cache, but it runs none of the platform's logic.
It keeps serving. The origin resolves a request by reading the route object, then the immutable manifest, then the blob — all from storage, with no live call to the control plane. An outage in the API affects new deploys and dashboard actions, not traffic to already-published sites.
See how it fits your world.
Tell us what you have in mind. We can help you explore the product and its current availability.
OUR PRODUCTS
More from Tanvrit.
Useful products for the people, plans and everyday work that matter to you.