Infralane documentation
Deploy and operate applications without managing the underlying cloud infrastructure yourself. These guides take you from your first resource pool to a running application, then show you how to monitor deployments, work with teammates, and manage billing safely.
New to Infralane? Complete the quickstart. It explains the shortest path from an empty workspace to a live application.
Start here
Learn how workspaces, projects, resource pools, applications, and deployments fit together.
Understand the platformCreate capacity, choose a source, review the configuration, and follow the deployment.
Deploy your first applicationConnect a repository, choose a branch, and configure the build.
Deploy from GitHubBring a ready-made image and configure how it runs.
Deploy an existing imageOperate your applications
What Infralane manages
You choose the application source, runtime shape, resource allocation, environment values, and storage requirements. Infralane turns that configuration into a deployment and gives you one place to inspect its status and runtime output.
The platform supports three common application shapes:
| Application type | Use it for | Public port |
|---|---|---|
| Web service | APIs, websites, and other long-running HTTP services | Required |
| Static site | Frontends that produce a directory of built files | Required by the deployment form |
| Background worker | Queue consumers, scheduled-style workers, and continuous background processes | Not used |
You can deploy from a Git repository or an existing Docker-compatible image. Availability of individual controls can depend on your workspace permissions, account access, and current platform plan.
Treat changes to production applications carefully. Saving an application configuration section starts a new deployment. Review the affected section and watch the new deployment before considering the change complete.
Documentation principles
These pages describe the customer-facing product. Values such as current prices, available regions, limits, roles, and payment methods are shown by the dashboard at the time you act; the dashboard is the source of truth when a value differs from an example in this documentation.
Never place passwords, access tokens, private keys, or secret environment values in support messages, screenshots, repository URLs, application names, or logs.
To permanently close your account, follow the Infralane account-deletion process.