Welcome to Parslinks
Parslinks is a deployment platform for containerized services — from Git push to global traffic
Welcome to Parslinks
Parslinks is a deployment platform for web applications and services. Connect a Git repository (or an image or a template), and Parslinks builds it, stores the result as an immutable artifact, deploys it onto a regional replica-set, and routes public traffic to it through a managed edge with automatic TLS.
How Parslinks is organized
Everything you create lives inside this hierarchy:
Workspace
└── Project
├── Services (git | image | template | resource)
└── Environments (production | preview | custom)
└── Instances (service × environment)- A Workspace is your top-level tenancy: members, invitations, and billing.
- A Project is a container that groups services and environments. It is not deployable by itself.
- A Service is the unit of source code, build configuration, networking, and resource attachment.
- An Environment is an isolated copy of the whole project graph — production, one per pull request (preview), or any custom branch environment.
- An Instance is a service placed into an environment. It holds that environment's deployment pointer, variables, clone policy, and pause state.
Getting Started
Create a workspace, add a project, deploy your first service.
Deployments
Immutable releases, aliases, and how traffic moves between them.
Domains & TLS
Custom domains, platform hostnames, and certificate handling.
Workspaces & Projects
Tenancy, membership, and the project graph.
Core concepts
| Concept | Meaning |
|---|---|
| Build | An execution attempt: logs, status, runner |
| ArtifactSet | Immutable build/upload output stored by content hash |
| Deployment | An immutable release; never modified once READY |
| Alias | A mutable traffic pointer to a READY deployment |
| Domain | Your hostname, routed only through an Alias |
| Instance | Service × Environment, with its own variables and placement |
| Workload | The regional replica-set running an instance |
Two rules worth internalizing early:
- Deployments are immutable. Once a deployment is READY its artifact, environment snapshot, and runtime spec never change. Traffic moves by repointing an alias — not by mutating the deployment.
- Placement is separate from release. Scaling (how many replicas, in which region) is configuration on the instance. It never rebuilds or redeploys.