Pailot
How does a boxed copilot differ from empty n8n?
| Pailot | n8n | |
|---|---|---|
| First difference | Copilot drafts the canvas from a brief | An engineer picks nodes by hand |
| What ships | A localized boxed stack, installed locally | An empty constructor |
| Publish | Web chat first, then API or A2A | You wire every exit yourself |
| Import | No button that moves an n8n scenario over | You rebuild the graph in another tool |
How is a process assembled?
A copilot drafts the first version from a brief. The manager still reviews the canvas. There is no public template store and no n8n import button.
- State the job in plain language.
- The copilot picks steps, systems and knowledge, then links them.
- You see every step and can fix one by hand.
- The copilot then runs a test, repairs what broke and publishes the process.
What is not in the integrations list?
Copilot, the language model, document search, speech, file parsing and the browser step are core of the box, not another connector. Domestic connectors are Bitrix24, amoCRM, MAX, VK and Telegram. The rest come from the catalog when they already live in the contour.
Access is by request on https://pailot.ru. There is no self-serve signup.
Who should stay on n8n?
Stay on n8n if you want an empty canvas that an engineer wires in an evening. Same category, different delivery.
- You want to pick every node yourself.
- You need a button that imports an n8n graph. That button does not exist.
- You want a public per-run tariff. Price here is on request.
What is in the box
Core of the delivery, not a connector list. Integrations sit under this.
- Copilot
- Drafts the process from a brief, checks links and publishes. At install time you choose a cloud copilot with redaction or a copilot that stays on your servers.
- Language model
- An LLM runs the agent step: reads text, decides, writes the reply. In the contour that model sits on the customer’s hardware.
- Document search
- RAG answers from your files and shows the source. The index stays in the contour.
- Speech and diarization
- Speech-to-text transcribes audio and video. Diarization splits speakers. A meeting can become a protocol or a reply in the same thread.
- Document parsing
- PDFs, spreadsheets, audio and video are parsed on-site. The file does not have to leave for a third-party parser.
- Browser step
- The process opens a live page and works like a clerk when no connector exists.
Domestic connectors in the box: Битрикс24, amoCRM, MAX, VK, Telegram. The rest come from the catalog (162 blocks and connections) when they already live in the company contour.
Where an agent can answer
| Channel | What it does |
|---|---|
| Web chat (fastest) | The fastest way out: the process becomes a chat page. A person types, the agent answers. Use it before wiring other systems. |
| API | Your system starts the process with a request and reads the result. |
| A2A | Agent-to-Agent: publish the process so other agents can call it over the A2A protocol. |
| MCP | Model Context Protocol: publish the process as a tool another assistant can call. |
Questions
- Is this a replacement for n8n?
- Same category, different delivery. The first difference is the copilot. n8n is an empty constructor. Pailot is a localized box installed locally. There is no button that moves an n8n scenario over.
- What does it cost?
- On request. There is no public per-run tariff.
- How do we publish an agent fastest?
- Web chat: a link, a person types. API and A2A come when another system must call the process.
- Can a manager run it without an engineer?
- The manager describes the job and reviews the canvas. A wrong step is fixed by hand. An engineer is not required for every new scenario.
- How do we get access?
- Submit «Получить доступ» on https://pailot.ru. There is no self-serve signup.