Core Concept
Service Types
We pick a service type for you during setup. Here's what the four types actually mean and what changes after you deploy.
The Four Types
What each type is for
Each type changes how your service runs and what you see on the detail page.
Web Service
A normal HTTP app with a public URL that people visit in the browser.
After deploy
A live URL, deploy history, activity, live logs, secrets, and settings.
Scheduled
Code that should run on a schedule instead of waiting for web traffic or incoming requests.
After deploy
A schedule, Run Now, execution logs, history, activity, secrets, and settings.
Function
An endpoint that receives events from another system, like GitHub, Stripe, or a custom webhook source.
After deploy
A webhook URL, request history, activity, secrets, settings, and test-event tooling.
Background Worker
A long-running process that just keeps running, like a queue consumer, daemon, or poller with no URL and no schedule.
After deploy
Live logs, deploy history, activity, secrets, and settings.
How To Choose
Four quick rules of thumb
- 1. If people visit it in a browser, it's a Web Service.
- 2. If another system sends events to it, it's a Function.
- 3. If it runs on a timer, it's Scheduled.
- 4. If it just keeps running in the background, it's a Background Worker.
Why It Matters
What changes after you deploy
Your service type determines what you see first on the service page.
-
Different default tabs. Web services open to History; functions open to Requests; scheduled and background workers open to Logs.
-
Different controls. Web services show the live URL. Scheduled services get a schedule and a Run Now button. Functions get a webhook URL. Background workers stream live logs.