seenode Documentation
seenode takes an application from a Git repository to a running service on a public HTTPS URL, and keeps it running. You bring the code, a build command, and a start command; the platform handles the container, the certificate, the load balancer, and the redeploys.
These docs cover web services, background workers, and managed PostgreSQL and MySQL.
Tip (New here? Start with the tutorial)
Deploy your first app walks you from a forked sample repository to a live HTTPS URL in about five minutes. There's no code to write, and nothing to configure beyond confirming what seenode detects. It's the fastest way to see the whole model in one pass.
Understand the platform
Read these when you want the picture rather than a task: what happens during a deploy, what seenode decides for you, and how the pieces fit together.
How seenode works
The deploy model, the decisions the platform makes for you, and the trade-offs behind them.Service types
Web services, background workers, and managed databases, and how they fit together.Web services
How a web service builds, starts, routes traffic, and scales.Deploy your app
Framework-specific guides for getting an existing project running. Pick your language, or see all of them on the how-to guides page.
Python
Django, FastAPI, and Flask.JavaScript
Express, NestJS, Next.js, Astro, and React / Vue / Angular SPAs.Go
Gin and Fiber.Elixir
Phoenix.Background worker
Queue consumers, schedulers, and long-running jobs with no public URL.Run it in production
Once your app is live, these are the tasks that come up next: giving it a domain, giving it a database, and giving it more capacity.
Custom domains
Point your own domain at a service, with automatic HTTPS.Databases
Create managed PostgreSQL or MySQL and connect your app to it.Scaling
Move to a larger instance, or run load-balanced replicas.Persistent storage
Attach a volume for files that must survive a redeploy.Managing a service
Environment variables, deploys, rollbacks, logs, and metrics.Troubleshooting
Fixes for 502s, failed builds, and framework-specific errors.MCP
Connect Cursor, Claude Code, and other AI agents to seenode via MCP.Agent Skills
Install seenode Agent Skills manually until marketplace plugins are available.Look something up
Precise, checkable detail: what runtimes exist, what things cost, and how to drive seenode from a script.
Runtimes and versions
The language runtimes available, and the versions you can select.Pricing and billing
Instance sizes, database tiers, storage prices, and the credit model.API
Base URL, authentication, and endpoints for automating deployments.