Service types

Most applications on seenode are built from a combination of these three services.

Web services

A web service runs any application that listens for and responds to HTTP requests: a web app, a REST or GraphQL API, or a server-rendered site. seenode builds your code, runs it behind a load balancer, and exposes it at a public *.seenode.app URL with a free, auto-renewing SSL certificate. You can also attach your own custom domain.

Web services are the only service type with a public URL. See Web services for how they build, run, and scale.

Worker services

A worker service runs a long-lived process in the background with no public URL: a queue consumer (Celery, RQ, BullMQ, Oban), a scheduler, a data pipeline, or a bot. A worker is deployed just like a web service but has no port to expose and isn’t reachable from the internet; it can still reach your other services over the private network and connect to a database.

Databases

A database is a fully managed MySQL or PostgreSQL instance. seenode provisions it, gives you connection details, and handles the underlying cluster. Databases are reachable from your other services over a private network, or publicly if you need external access.

How they fit together

A typical application is a web service for the public API or site, one or more worker services for background jobs, and a database for state, all in one workspace, communicating over a shared private network. Every service is billed from the same prepaid credit balance, deducted daily based on what’s running.