Documentation

Get started with Infrastry

Connect a repository, let Infrastry prepare the production plan, and follow your application from source code to a healthy URL.

Last updated

Before you begin

Infrastry starts with the code you already have. You do not need to write infrastructure configuration before creating an application.

  • Use a public Git repository, or connect GitHub to choose an authorized private repository.
  • Know the branch you want to deploy. Infrastry uses main unless you select another branch.
  • Make sure the repository contains the application code and the dependency files needed to build it.

Note: A repository can include a Dockerfile, but it does not need one. Infrastry can prepare the build instructions from the application it finds.

Create your application

Sign in, choose your team, and select New App. Paste a repository URL or choose a repository from your connected GitHub account, then start the analysis.

  • Infrastry checks out the selected branch and identifies the services, runtimes, and data dependencies it needs.
  • Review the proposed application before deployment begins.
  • Keep the application page open to follow each stage as it completes.

Review the production plan

The app spec is the readable plan Infrastry creates for your application. It records what will run, how it will build, which environment values it expects, and what persistent resources it needs.

  • Open App Spec to inspect the detected components and their build and run commands.
  • Add any required environment values before launching a deployment.
  • Confirm the selected runtime and region in Settings.

Note: While we’re still early: Treat the app spec as a review point. If the detected plan does not match your application, correct the source configuration or update the plan before relying on the deployment.

Follow the launch

A deployment moves through source checkout, build, release, startup, routing, and health verification. The application overview shows the current outcome while Activity and Logs provide more detail.

  • A healthy application displays its live URL on the overview page.
  • A failed deployment keeps its history so you can review the stage that needs attention.
  • Future deployments create a new recorded attempt without removing earlier results.
Next guide Deployments