Pailot is not published as a one-click template on Railway, DigitalOcean Marketplace, or similar catalogs. The vendor installs the same contour on a VM or Kubernetes cluster the customer already operates.
Request a contour install at pailot.ru. Price is on request.
Typical customer infrastructure
Any Linux VM the customer controls is enough for a compose-based contour, if it meets the sizing outline. Common choices:
| Environment | Typical shape |
|---|---|
| On-prem VM | Ubuntu LTS, Docker Engine, Caddy or Nginx |
| Private cloud VM | Same as on-prem; security groups instead of a physical firewall |
| Managed Kubernetes | Vendor-applied workloads; see Kubernetes |
SSH, disk, and network access are arranged with the customer before install. The vendor does not ask you to clone a public repository onto the VM.
Managed PostgreSQL (optional)
Production contours often use a managed Postgres with the pgvector extension:
- AWS RDS / Azure Database / Cloud SQL — enable pgvector
- Supabase / Neon — pgvector is usually available
The vendor sets DATABASE_URL to that instance, for example:
DATABASE_URL="postgresql://user:pass@host:5432/pailot?sslmode=require"DNS and TLS
Create an A (or AAAA) record for pailot.yourdomain.com (or the hostname in the contract) pointing at the contour. Certificates are issued during install.
What not to do
- Do not deploy a public third-party workflow builder and relabel it Pailot
- Do not use a marketplace button that installs a different product
- Do not publish the contour on the open internet without the agreed reverse proxy and access controls