Introduction
Teral builds your code, runs it, and puts it on the internet.
You connect a GitHub repository or point Teral at a container image. Teral turns it into a running app with HTTPS URLs, keeps the old versions around for rollbacks, and gives every branch its own preview.
What Teral handles
- Builds. Teral detects your language and builds an image without a Dockerfile. If you have one, Teral uses it instead.
- Deployments. Every push becomes a deployment. Each deployment is immutable, so you can always go back to one that worked.
- URLs and certificates. Every deployment gets
teral.runaddresses right away. You can add your own domains, and Teral issues and renews the certificates. - Scaling. Each app runs one or more instances per region and scales between the bounds you set.
- Traffic rules. The gateway in front of your app can block requests and record them before they reach your code.
- Insight. Runtime logs, request logs and metrics are part of the dashboard.
Where to start
Deploy your first app
From a repository to a live URL in a few minutes.
How Teral is organized
Workspaces, projects, apps, environments and deployments.
Frameworks
Next.js, Node.js, static sites, Python and Go.
GitHub
Which pushes deploy where, and how to control it.
Troubleshooting
What to check when something doesn't work.
API
Automate everything the dashboard does.
Teral is in beta. If something is unclear or broken, tell us on Discord or at support@teral.dev.