AI tools are made for building. HostSpry is made for running.
HostSpry takes the app you built with an AI tool from its repository to an isolated production environment — with a plan before every change, your approval, and a report of what was verified.
Today: code on GitHub with a Supabase backend, or a backend with its own Dockerfile.
Publishing got easy. Staying in production didn’t.
I don’t know what I’ll pay this month.
On usage-based hosting, traffic above your quota becomes an invoice — bots included.
My spend limit took the site down.
Where a spending cap exists, reaching it usually pauses production.
The code is mine. The backend isn’t.
Code exports easily. A managed backend, its files and its secrets often don’t.
Is my app exposed?
Security settings generated by an AI tool need to be checked before real users arrive.
Your AI tool built the app. HostSpry runs it — and nothing changes without you.
One place to run what you built.
- 01
Plan, approve, then run.
Before anything is written you see the plan: every step, check, warning and blocker. Nothing touches your environment until you approve it.
- 02
Production-grade by default.
An isolated environment with its own database, builds without privileges, and secrets sealed where they run.
- 03
Every change verified.
Each part is checked afterwards. A check that cannot reach a verdict is reported as indeterminate — never as a pass.
From repository to production, step by step
- 01
Connect
Install the HostSpry GitHub App on the repositories you choose. It reads what the analysis and the build need, and it never writes.
- 02
Analyse
We inventory your stack, backend, migrations and the names of the variables your app expects — and say plainly what we can’t run yet.
- 03
Plan and approve
Every step, check, warning and blocker is shown before anything is written. Nothing runs until you authorise it.
- 04
Build and run
Your code, including your own Dockerfile, is built without privileges and runs in an isolated environment with its own database.
- 05
Verify and report
Each part is checked. You get what passed, what failed and what could not be told.
What your app gets in production
Items marked Coming soon are what we are building next. They are not available yet.
- Available
Isolated environment, own database
Network, storage and database separated from every other customer.
- Available
Sealed secrets
Generated where they run, mounted read-only, never sent back to your browser.
- Available
Encrypted backups
Encrypted, with restore tested.
- Available
Priced per project, not per visitor
Hosting is not billed per visitor or per bandwidth. What your app spends with other providers — AI APIs, payments, e-mail — is billed by them. Plan prices come before general availability.
- Coming soon
Custom domain with HTTPS
Your own domain, with HTTPS set up and renewed for you.
- Available
Your API keys reach your app
Keys you provide for payments or e-mail, delivered to your app without passing through your browser.
- Coming soon
Build and run logs
Read what happened during a build and while your app runs, with secrets removed.
- Coming soon
Access to your files and database
Your project’s files and database only — never another customer’s.
- Coming soon
Scheduled backups you can download
Kept away from the server that runs your app.
- Coming soon
Export your project
Open formats, generated by you, without a ticket or a fee.
- Coming soon
Usage alerts before limits
Sustained use above your plan brings an alert and a recommendation. No paid change happens without your approval.
Move your Supabase backend. Check every part.
Schema, extensions, users and identities, table data and storage files move with a restore point taken before the first write. Your source is opened read-only and never written to.
Active sessions don’t carry over — your users sign in again after the move.
Proof, not promises
- Restore point
snapshot-do-destino - Extensions
instalar-extensoes - Schema
copiar-schema - Auth users
copiar-auth - Data
copiar-dados - Storage
copiar-storage
- steps applied
- 6
- checks passed
- 11
- checks failed
- 0
- indeterminate
- 0
One run, in our laboratory, against a disposable destination. Not a customer. Not a success rate.
Where it runs
Each model is described by what is available today.
Managed Shared Hosting
The entry product. Your app runs in its own isolated environment on a host shared with other customers — separate processes, network, storage and database. HostSpry runs the infrastructure.
Available in the private beta
Managed VPS
A virtual server for one customer only, with one or several of your projects on it, isolated from each other by default. HostSpry still manages it.
Coming soon
Managed Dedicated Server
A physical machine for one customer only — not a VPS. For larger apps and heavier workloads. HostSpry manages the infrastructure.
Planned
Start with a migration review
Tell us where your app lives today. A person reviews your repository and backend and replies by e-mail with what we can run now, what we can’t yet, and the next step.
- Tell us about your app — where the code is and what backend it uses.
- We review it and reply by e-mail. HostSpry is in private beta: there is no self-serve sign-up yet.
- If we proceed, the first run is a rehearsal against a disposable destination.
Built with AI. Run with care.
Tell us about your app. We’ll reply with what it takes to run it in production.