Glossary

Application
A customer-configured workload deployed from Git, a Docker image or ZIP source.

Application allocation
The CPU and memory assigned to one application from its resource pool.

Application type
The workload shape: web service, static site, background worker or TCP/UDP service.

Branch
A named line of development in a Git repository. Infralane deploys the branch selected in application configuration.

Build command
The command used to install, compile, or otherwise prepare source code for deployment.

Crane
The agent installed on a server to carry out deployments and connect application operations to Infralane.

Private hostname
A server-network name reachable by applications in the same project on the same server.

Deployment
A single attempt to release an application configuration.

Environment variable
A named runtime value provided to the application. Values may contain secrets and must be handled carefully.

Image
A packaged, runnable application artifact referenced by registry, repository, and usually a tag.

MFA / two-factor authentication
An additional sign-in check using a time-based code from an authenticator app.

Mount path
The path inside the application where a persistent volume is made available.

Persistent volume
Storage intended to remain available across application releases, mounted at a configured path.

Port
The internal network port on which a web service listens.

Project
An organizational boundary inside a workspace that contains applications and resource pools.

Public endpoint
The domain or URL assigned to a web-facing application.

Resource pool
The capacity of a connected customer-owned server or optional hosted server, shared by applications in a project.

Root directory / working directory
The repository directory that contains the application being built, especially important in a monorepo.

Runtime
The language environment selected for a Git source build, such as Node.js, Python, or Go when offered.

Start command
The command that launches a web service or background worker and remains running.

Static output directory
The folder containing the built files for a static site.

Workspace
The shared top-level area that owns projects, members, integrations, and billing context.