Services
The three kinds of compute you can deploy to Appentic.
Appentic has three kinds of deployable compute, collectively called services. They share the same build pipeline, the same environment variable handling, the same logs, and the same metrics. What changes between them is how they're triggered and whether they're exposed to the outside world.
Web services
Long-running HTTP servers that handle public traffic. Appentic gives each one a public URL on *.appentic.app with a TLS certificate issued automatically, and you can attach your own custom domain. A web service is what you'd deploy for a web app, a REST API, a GraphQL server, or anything else that needs to answer incoming HTTP requests.
Web services autoscale based on request concurrency. You can set a minimum instance count if you want to avoid cold starts, or let them scale to zero when idle to save money.
Workers
Long-running background processes without a public URL. Workers are the right fit for queue consumers, websocket brokers, event pollers, or anything else that needs to sit and listen without being reachable over HTTP. They start up, stay up, and restart if they crash.
Because they don't receive HTTP traffic, workers don't need a PORT environment variable and don't autoscale on concurrency. You pick how many instances to run and Appentic keeps them alive.
Cron jobs
One-shot containers triggered on a schedule. You give Appentic a cron expression and a command, and it runs the container at the scheduled time, captures the output, and shuts it down. Cron jobs are the right fit for nightly exports, cleanup tasks, scheduled reports, and anything else that needs to happen at a specific time.
What they share
All three service types are built from the same GitHub repository pipeline, get the same environment variables injected, log to the same dashboard, and support the same rollback workflow. So you can move logic between a web service, a worker, and a cron job without changing how you build or deploy.