Sapient Deploy (hosting)
Sapient Deploy is Sapient’s own hosting. Pick it as a product’s deploy target and your factory ships to a live, public URL with no Vercel, Netlify, Cloudflare or cloud account of any kind.
What it enables: a product goes from merged code to something you can open in a browser and send to someone — usually within the same sprint that built it.
What gets deployed
Section titled “What gets deployed”Sapient Deploy handles both halves of a typical product:
| Part | What happens |
|---|---|
| Frontend | Your product’s build output — React, Vue, plain HTML, anything that builds to static files — is uploaded and served. Single-page apps get client-side routing (a deep link loads the app, a missing asset still returns an honest 404). |
| API backend | If the product has a Go backend, it’s compiled, packaged, and run as its own container. It scales to zero when nothing is using it. |
The two are served on one origin: your frontend calls /api/… on its own hostname, and Sapient
routes it to the backend. No CORS configuration, no second URL to manage.
Your product’s address
Section titled “Your product’s address”Each deployed environment gets a real hostname with a real certificate:
https://<product>.<your-company>.sapient.worksHTTPS is provisioned automatically the first time the hostname is used. Bringing your own domain is supported too, and gets its certificate the same way — but it needs a little more than a DNS pointer: connect a DNS provider, set the domain on your factory, and let Sapient write the record so ownership is proven. Your seats handle the mechanics.
What you can see and undo
Section titled “What you can see and undo”Everything on the ordinary environment page: deploy history, which version is live, and one-click rollback to any previous deploy.
Health is checked once after each deploy. If the new version is already erroring or slow, the factory opens a rollback recommendation for you to approve. It’s a check, not a soak — a product that hasn’t been exercised yet reports no data, and no-data never triggers a recommendation. For continuous watching, use the Observability screen, which reads Sapient Pulse live.
Scope and limits
Section titled “Scope and limits”Sapient Deploy is built for products your factory is developing, demoing, and iterating on. It is not a production hosting platform for serious traffic: there’s no CDN, no autoscaling beyond a single instance per app, no custom runtime configuration, and no SLA.
When a product is ready for real users, connect Vercel, Netlify, Cloudflare, or a cloud target and switch the environment over — see Deployments and environments. For a static frontend that’s close to just a setting change. A product with a backend has more to it: the new target has its own build, runtime and environment conventions, and anything wired to Sapient Base or Sapient Pulse needs repointing. Your seats do the work, but it is work.