Home/Docs

Wrenship docs

Put what your AI builds on air. Static sites and server-rendered apps run on Wrenship's global edge, with a database and file storage when your app needs them.

What you can run

	Static site	Server-rendered app
For	HTML, React, Vue, Svelte, Vite, Astro and other builds that output files	Next.js, Nuxt, Astro on the server, Hono, API routes
Where	Wrenship's global edge, close to every visitor	Wrenship's global edge, running your code for each request
Plans	Free, Starter, Edge Pro	Starter (1 app), Edge Pro (10 apps)
Data	—	SQLite or Postgres database and file storage

You don't have to pick. Wrenship reads your code and tells you which one it is. See Frameworks for exactly what is detected.

Everything runs on Wrenship. There is no machine for you to set up, patch or log in to.

Ways to deploy

Upload. Drop a folder or a .zip at app.wrenship.com/new.
Git. Connect GitHub or GitLab. Every push to your production branch goes live, and on Edge Pro every pull request gets its own preview.
Terminal. npx wrenship deploy from any project folder. See Deploy from the terminal.
From an AI app. Connect Claude, ChatGPT or Cursor once, then ask it to deploy. See Connect an AI app.

The Quickstart walks through each one.

What happens on every deploy

Wrenship detects the framework and builds it in a fresh, isolated builder that is thrown away afterwards.
The build is scanned for leaked secrets. A .env file is never published.
The new version is published to the edge and switched over at once.
If anything fails, the version that was live stays live. Any earlier build can be put back with one click.

Where to go next

Environment variables and custom domains
Databases, file storage and backups
Security: how your apps and data are kept apart and safe