Pailot is a commercial product. ООО «Профитайзер» (Profitizer) installs it in the customer's contour (on-prem servers or a private cloud the customer controls). There is no public git repository, no self-serve Helm chart, and no marketplace one-click install.
Access and pricing are on request at pailot.ru.
Do not clone third-party workflow builders or public upstream repos and treat them as Pailot. The bits that run in a customer contour come from the vendor delivery.
What a Contour Install Includes
The vendor delivers and starts the platform. A typical layout:
| Component | Typical port | Role |
|---|---|---|
| Application | 3000 | Main web app and API |
| Realtime | 3002 | WebSocket server |
| Database | 5432 | PostgreSQL with pgvector |
| Migrations | — | Schema updates (run once per release) |
Exact image names, compose service names, and hostnames are in the delivery runbook — they are not published here.
Operator Pages
These pages assume you already received a delivery. They describe configuration and day-2 operations, not a public install path.
Docker
Compose-based contour: reverse proxy, local models, backups
Kubernetes
When the customer contour is a Kubernetes cluster
Cloud Platforms
Private VMs and managed databases — not a public marketplace
Environment Variables
Configuration the vendor sets at install time
Troubleshooting
Common operator checks
Sizing (typical starting point)
The vendor confirms hardware after seeing the workload. A common starting outline:
| Resource | Minimum | Comfortable |
|---|---|---|
| CPU | 2 cores | 4+ cores |
| RAM | 12 GB | 16+ GB |
| Storage | 20 GB SSD | 50+ GB SSD |