Application types

The application type tells Infralane how a workload behaves. Choose it based on the process you run, not the programming language.

Web service

Choose Web Service for an HTTP application that starts a server and keeps running. Examples include APIs, server-rendered sites, and web backends.

You must provide a valid port and, for source builds, a start command. The application must listen on the configured port. If it listens on a different port or only binds to an inaccessible local interface, the deployment may complete its build but fail to serve traffic.

Static site

Choose Static Site when a build produces files such as HTML, CSS, JavaScript, and images in an output directory. Common directory names include dist, build, and framework-specific output folders.

Set the output directory to the path created by the build command, relative to the selected repository root directory. A typo or wrong monorepo root can make an otherwise successful build appear empty.

Background worker

Choose Background Worker for a long-running process that does not receive public HTTP traffic. Workers do not use a public port. The process must continue running; if the command finishes immediately, the workload stops.

Git source or image source?

Choose Git when you want Infralane to run your build command from a repository. Choose an image when your release process already publishes a runnable, versioned artifact.

Question	Git repository	Existing image
Does Infralane run a source build?	Yes	No
Do you select a language runtime?	Yes	No
Do you provide build settings?	Yes	The image already contains the runnable app
Can it be a web service, static site, or worker?	Yes	Yes, according to the current form

Application names and descriptions

Use a short, stable name. Application names cannot be changed after creation. Descriptions can be updated and should explain the application’s role to teammates without containing secrets or customer data.