Know where every piece of work stands, and what should happen next.

One workflow per process, not one for the whole company. A job, a claim, a ticket or an onboarding each gets its own: the states it moves through, the activities each state permits, the form each activity requires, and one history of who did what. Start with the process that generates the most “any update?” messages. Add the next one when it has earned its place.

No, and it should not. Those tools execute: they move data, call systems and run the steps that never need judgment. Inistate holds the workflow around them — the state the work is in, what may happen next, who may act, and what already happened. Your automation performs an activity through the Inistate app on n8n, Make or Zapier, or straight at the REST API and webhooks, and the state it lands in can trigger the next automation. Many automations. One governed workflow.

Through MCP. Inistate is in the Claude and ChatGPT connector directories, and any other MCP client connects the same way. Once connected, the agent has no private route into your data: it can only perform the activities the current state permits, with the form each one requires, within the permissions you give it — never wider than the person it acts for. An activity your rules reserve for a person, like approving spend, stays with a person. It reads the same way it writes — ask it how many jobs are past their SLA this week and it answers from the live records, not an export.

It stops and asks. Past a confidence threshold the agent pauses for a person instead of guessing, and the question and the answer stay on the record. Every action it does take carries its reasoning, its sources, its confidence and the model used, on the action itself rather than in a separate log. So when something needs a second look you can see exactly what happened and why — and because the workflow rules apply to the agent too, it could not have skipped a required step to get there.

No. Describe the process in a sentence, forward the message you usually get, or photograph the form you use today, and Inistate turns it into a structured starting point — states, fields, owners and history — rather than a blank canvas. You shape it from there, without code. Bring one process, not the org chart; the rest of the operation joins one workflow at a time.

Free forever, no card. It includes 2 users, plus an actor seat that connects the integrations and AI clients and can go to a third person, an automation or an AI agent; 500 active records plus 500 read-only; 1 GB of files; 30 days of change history; and unlimited modules, guests, documents, reports and built-in automations for notifications, reminders and alerts. It also comes with 1,000 AI credits, one-time, which is about enough for the AI to build one complete workflow with you. When you need more people or connections, add up to 5 more actor seats at US$8 a month each. If you outgrow a limit we warn you and suggest the next plan — we never refuse to take in your work. Details on pricing; for teams of 50 or more, see enterprise.

In credits, shared by the whole workspace, and they never expire. Plans buy the capacity — users, records, storage, history — and AI is metered separately, so a quiet month costs nothing extra and you are never paying a monthly fee for AI you did not use. Ordinary work such as logging a job from a photo, chasing an approval or drafting a document costs far less per turn than asking the AI to design or analyse something. Top up with a pack whenever you want more.

Yes to both. Inistate runs on the web and on iOS and Android, so a technician completes the job and attaches the photo from the site, and the record updates for everyone at once. For people outside your team — a customer confirming the fix, a client uploading year-end documents — you share a form or a record with them as a guest. Guests are unlimited, even on the free plan.

Those tools give you a place to put work, and increasingly an agent to help with it. But your team is still the workflow engine: the rules live in columns, buttons and habits. In Inistate the workflow is the product: the state, the permitted activities, the required forms and the history are what people, AI and automations all act through. Jira is built around tickets, sprints and epics for software teams; Inistate is built around states, activities and forms for any operation. App builders like Glide or Jotform build you an app and hand it back; Inistate stays inside the workflow and runs it with you.

Do — through Inistate. On its own, a chat gives you an answer in a window and forgets it when the conversation ends. Connected to a workflow, the same assistant performs activities on real records, within the rules, with every action on the history, and it is still tracking the work when the day ends. Keep the assistant you already use. Give it something that persists.

Inistate is ISO/IEC 27001:2022 certified, and the architecture is protected by US and Singapore patents. Because who did what, with which input, from which state, is written on the record itself, the audit trail is a by-product of the work rather than something reconstructed from exports and screenshots under deadline. For regulated teams, those fields are evidence your compliance team can map to obligations such as EU AI Act Article 14, FINRA Rule 3110, the Colorado AI Act and HIPAA audit controls. See trust and compliance and the privacy policy.

Work that fits inside a single automation run. A form that emails a spreadsheet row, a nightly sync, one isolated approval — your automation tool already handles those, and a workflow around them is overhead. Inistate is for work that outlives the run: a job, case, request, order or claim that moves through several states, that people and systems both touch, and that somebody keeps asking about.