Unlimited users. One flat price.
An operation has more people touching the process than people working in the tool. In Jestor everyone gets a login, on any plan, and the invoice does not move.
Everything an operation needs to run its processes: conditional phases, forms, SLAs, approvals, portals, automations and AI agents. You can start for free and build with AI, with an unlimited-users option.
Jestor is an AI operations platform: a relational database, apps, automations and agents, delivered ready by our team and adjusted by prompt. Below, the features a process team expects to find, and how each one exists in Jestor.
| Feature | Jestor |
|---|---|
| Unlimited users | Yes |
| Pipes and phases (one kanban per process) | Yes |
| Conditional phases | Yes |
| Conditional fields | Yes |
| Public and internal forms | Yes |
| SLAs and time per phase | Yes |
| Approvals by amount, role or phase | Yes |
| Connections between processes | Yes |
| Relational database | Yes |
| Automated emails and an inbox per process | Yes |
| Portals and external access without a seat | Yes |
| Automations and integrations (400+) | Yes |
| WhatsApp, Slack and Teams | Yes |
| AI agents and OCR | Yes |
| Dashboards and reports | Yes |
| Mobile app (iOS and Android) | Yes |
| Open API and MCP | Yes |
| Field-level permissions | Yes |
| Audit trail and history | Yes |
| SOC 2 Type II and LGPD | Yes |
Every feature on the list, and what it does in Jestor. Sources at the end of the page.
| Feature | Jestor |
|---|---|
| Users | An unlimited-users option on Hero AI, Growth, Pro, and Enterprise, one flat monthly price |
| Pipes and phases | Each process is a kanban on top of a table. Multiple kanbans on the same table, indicators per phase, colors and buttons per card. |
| Conditional phases | Phases that appear or advance based on field values: a request above $10k goes through the board, below it goes straight to purchasing. |
| Conditional fields | Fields that appear, hide or become required based on the previous answer, in forms and on cards. |
| Forms | Public forms for customers and suppliers, internal forms for the team, with conditionals, signatures and connected-record blocks. Submitters never need a seat. |
| SLAs and time per phase | Time in each phase per record, aggregate time, SLA on tickets and visual indicators on the kanban. |
| Approvals | Structured decisions by amount, role or phase: purchasing, reimbursements, vendor onboarding, change requests. |
| Connections between processes | Relational database with n:m, n:1 and 1:1 links. An order knows its supplier, contract and invoice without duplicating data. |
| Database | Relational tables with formulas, views and an allowance for records that grows with add-ons. |
| Emails | An inbox per table: email becomes a ticket or record with history, SLA and an owner. Automated emails per event and per phase. |
| Portals and external access | Public forms and portals for customers and suppliers to see and update only their own records, at no user cost. |
| Automations and integrations | 400+ native automations and integrations, chainable; Python, .NET or PHP steps when the rule gets complex. Omie, Conta Azul, Slack, Teams, DocuSign, Zapier, Make and webhooks. |
| Messaging | A WhatsApp agent turns messages from customers and field teams into records; notifications and actions in Slack and Teams. |
| AI agents and OCR | Chat-to-App, Ask Your Data, email agent, WhatsApp agent, OCR of invoices, receipts and documents into structured fields. |
| Dashboards and reports | Charts, indicators and speedometers on live data; Power BI connector on Enterprise. |
| Mobile | Apps for iOS, Android, Windows, macOS and Linux, with mobile-specific block positioning. |
| API and MCP | Open API, webhooks and MCP: Claude, ChatGPT, Cursor and any MCP client create tables, permissions and automations and read or update records. |
| Permissions | Rules by role, table and field on every plan. The AI inherits the same permissions. |
| Audit trail | History with user, IP and before/after values; automation run log; snapshots and restore of deleted records. Humans and AI in the same log. |
| Security | SOC 2 Type I and II, LGPD, regular pentests, MFA; SSO on the Enterprise plan. |
Jestor information from jestor.com/plans, jestor.com/ai and jestor.com/main-features, verified September 15, 2026.
An operation has more people touching the process than people working in the tool. In Jestor everyone gets a login, on any plan, and the invoice does not move.
Those are operations features, configured on the data model, not assembled as workarounds or generated as custom code you then have to maintain. Jestor ships forms, approvals, SLAs and kanban natively, with more than 400 automations. Python, .NET and PHP cover custom logic when you need it.
A new phase, a new field, a new approval: say it in Claude, Cursor, ChatGPT or Jestor’s prompt box and it's live. The AI can only touch what your role can touch, and every change, human or AI, lands in the same audit trail.
Hero AI and Enterprise include unlimited users. Growth and Pro can be one flat company price or per seat. You can start a free trial on Hero AI. Everyone involved in a process can have their own login, from the operations team to field staff, customers and partners. Permissions control what each person sees and edits. Per-seat pricing pushes companies to leave people out. The workarounds that follow, like shared passwords, public links and side tools, cost more in security, traceability and money than the seats they save.
Every employee can use the system, not just the few who justify a seat. Field-level permissions decide what each person can see and edit, so giving more people access doesn't mean giving everyone access to everything.
When every user costs extra, teams share data through public links to avoid buying seats. Anyone holding the link can open it, it can be forwarded, and there is usually no way to know who opened it. When everyone has a login, access is tied to a person and can be revoked.
A shared login turns five people into one user. You lose track of who created, edited or deleted each record. When someone leaves the company, the only safe move is to change the password for everyone. Individual users keep a clear history of who did what, and you can remove one person's access without affecting anyone else.
Security frameworks like SOC 2 rely on three core controls: unique user identification, least-privilege access and fast offboarding. Those controls also support the safeguards LGPD requires. Shared credentials and open links work against all three. Jestor is SOC 2 Type I and Type II compliant, and unlimited users make it practical to keep those controls in place for everyone.
Clients, suppliers and partners can log in to follow requests, submit information or approve steps. They see only what their permissions allow. There are no extra seats to budget for and no separate portal tool to buy.
The per-seat price is only part of the bill. When some people stay out, work moves to spreadsheets, email and WhatsApp, and data gets retyped. Companies often end up paying for a second tool to cover the people without access. A flat price removes the trade-off between cost and adoption.
Features built around people only work when the people are there. You can mention anyone in a chat, assign tasks and approvals to the right person, and send SLAs and notifications to whoever owns each step. The audit trail then shows who did what. Jestor’s AI also follows each user's permissions, which only works when each person has their own user.
Jestor is not affiliated with, endorsed by, or sponsored by Pipefy. “Pipefy” is a trademark of its owner. This page describes Jestor features as published on jestor.com/plans, jestor.com/ai, jestor.com/main-features and docs.jestor.com, verified September 15, 2026. Features and prices change; verify current offerings with each vendor. If something is wrong or imprecise, please let us know at [email protected] so we can update it.