Deploy with one prompt
Your coding agent reads the repo, writes the config and ships it. No dashboard to click through, no YAML to learn.
Frontend, backend, and database — described in one file and live on a real URL. Tell your agent to deploy. Hexclave runs the rest.
Free tier / No card required
01 Features
Hexclave Deploy puts your frontend, API and database on the same private network, behind a real URL, from a single prompt.
Your coding agent reads the repo, writes the config and ships it. No dashboard to click through, no YAML to learn.
Frontend, backend, database and workers deploy as one group and talk over a private network.
hexclave.deploy.ts describes every service. Review it in a PR, roll it back with git.
Every public service is live on HTTPS the moment it deploys. Bring your own domain when you're ready.
Choose per service. Keep the API warm, and let the frontend sleep when nobody's visiting.
When traffic spikes, capacity follows demand up and back down again. You don't touch a thing.
A real free tier. No credit card to get your first stack live.
02 How it works
Your agent does the setup. You keep the config in your repo, so every deploy is reviewable and repeatable.
Ask your agent to deploy. Hexclave's skill inspects the project and works out what needs to run.
It writes hexclave.deploy.ts into your repo. Tweak it, commit it, or leave it as is.
Services build, connect and go live together. You get a URL, and a custom domain whenever you want one.
03 Config as code
No console archaeology. hexclave.deploy.ts lives next to your code and is the single source of truth for what runs.
import { defineDeploy, secret, service } from "hexclave/deploy";
export default defineDeploy({
services: {
// Scales to zero when idle
web: {
type: "serverless",
public: true,
port: 3000,
env: { API_URL: service("api").url },
},
// Always warm, talks to the db privately
api: {
type: "server",
minInstances: 1,
port: 4000,
env: {
DATABASE_URL: service("db").url,
STRIPE_KEY: secret("STRIPE_KEY"),
},
},
// Never exposed to the internet
db: {
image: "postgres:16",
public: false,
volume: { path: "/var/lib/postgresql/data" },
},
},
});
04 Scaling
Drag the slider. Capacity is added and removed for you, and serverless services drop to zero when traffic does.
05 Pricing
$0to start
Everything you need to get your first stack live.
.deploy.built-with-hexclave.com URLhexclave.deploy.tsUsagepay as you grow
Remove the guardrails once real users show up.
06 FAQ
You ask your coding agent to deploy. Hexclave's Deploy skill inspects your project, generates hexclave.deploy.ts, provisions the services and returns a live URL. You can review and edit the file at any time.
Yes. Define them all in one file and they deploy together. Databases and internal services can stay off the public internet and talk to each other over a private network.
Serverless services scale automatically and drop to zero when idle. Always-on servers keep at least one instance warm. You choose per service.
Every public service gets an instant URL. When you're ready, add your own domain, set the DNS records shown in the dashboard and Hexclave verifies it.
Yes. You can start free without entering a card. The free plan uses serverless services that scale to zero. Always-on servers and longer runtimes are part of the Team plan.
Not in git. You reference them by name in your config, and the values are stored in your project's secret settings and injected per environment.
Your first deploy is one prompt away. Free to start, no card required.