Webserving
Processes and Internet Access
Each Tapitalee app can run one or more Processes. Of all the processes you define, only the default process is internet-facing — it is the sole process that receives public traffic routed through your app’s load balancer.
Any additional processes you create (e.g. worker, scheduler, mailer) are entirely optional and are intended for background work. They run inside your private network and are never directly reachable from the internet.
| Process | Internet-Accessible | Typical Use |
|---|---|---|
default | ✅ Yes | Web server, API, frontend |
| Any other | ❌ No | Background workers, cron jobs, etc. |
See the Processes reference for full details on creating and configuring processes.
Domains
Although optional, you will generally want to attach a custom Domain to each app so that your users can reach it via a friendly URL rather than the default Tapitalee hostname (*.dns.tapitalee.net).
Each app should have its own domain configured. See the Domains reference for how to add one.
Proxy (SSL / HTTPS)
A Proxy sits in front of your default process and handles HTTPS termination, forwarding decrypted requests to your app over the internal network. While a proxy is optional, it is strongly recommended for any internet-facing app.
Internet (HTTPS) → Proxy → default process (HTTP)Tapitalee offers two proxy options:
| Option | Description |
|---|---|
| CertWrapper | A Traefik sidecar container that runs alongside your app. Cost-effective; restarts with app deployments. |
| SecureProxy | A dedicated, independently-running Traefik ECS service. Enables zero-downtime deployments and can be shared across multiple apps. |
You only need one proxy per environment. For most production workloads, SecureProxy is the recommended choice because application deployments do not restart or interrupt the proxy service, ensuring uninterrupted HTTPS for your users.
See the SecureProxy add-on for setup instructions.