Runtime Security
Run production workloads with safer defaults built in.
Adios puts public traffic behind gateways, keeps secrets out of source, isolates runtimes, and supports private internal networking paths.
The hook
Why developers care
Raw servers make every security decision your problem: TLS, exposed ports, secrets, tenant boundaries, resource limits, and runtime logs.
How Adios handles it
- 1Deploy behind the Adios gateway.
- 2Use secret:// references for sensitive config.
- 3Run workloads with runtime boundaries and inspectable deploy state.
What you get
Platform pieces that make this work.
Gateway-before-runtime traffic model
Linux namespaces and cgroup limits where supported
WireGuard-backed private internal networking where configured
SOC 2 and ISO 27001 work in progress
Build path
Ship without turning a VM into your security project.
Deploy an API with managed TLS, secrets outside Git, runtime logs, and app workers behind gateway routing.
Deploy your first app on Adios.
Start with this feature, then add the rest of the platform as your app needs it.
Keep exploring
AI Coding Workspaces
Use the Adios agent inside a source-backed workspace, then inspect, edit, preview, commit, and deploy the code it creates.
Adios Deployments
Use adios.yaml and the Adios control plane to build, start, health-check, and promote app runtimes.
Managed App Hosting
Run long-lived app processes for common runtimes while Adios handles routing, logs, health, regions, and deploy state.