The operations app for organisations that have to prove what their AI did, not just that it ran.
Every action your people, your AI agents, and your automations take lands on one record-level history, and what may happen next is decided by the workflow rather than by whoever is acting. Start with one process, prove it against your own controls, then roll out.
Or start free on one workflow and bring it to the briefing.
The four questions your reviewers always ask
None of them are about whether the automation worked. They are about what happened to the case, who decided, and whether you can show it rather than rebuild it.
“Who approved this?”
The approval happened in a chat thread. Six months later there is nothing to point at except somebody’s memory of the conversation.
In Inistate the approval is an activity on the record, so its history shows who performed it, when, and from which state.
“What did the AI actually do?”
An execution log proves a job ran. It does not tell you what happened to the case, on what basis, or how sure the model was.
Every AI action is recorded with its reasoning, its sources, its confidence and the model, on the action itself.
“Who was allowed to act?”
Access is granted per tool and per integration, not per state of the work. The blast radius ends up being whatever the token allows.
Each activity says whether people, AI or both may perform it, and a record offers it only in the states that permit it. An agent works with the access of the person who connected it.
“Can you show us, not rebuild it?”
Evidence gets reconstructed from exports and screenshots under deadline, which is exactly when things get missed.
The history is written as the work happens, so the evidence is the record itself, not an export assembled afterwards.
What sits in the record instead
Audit fields are part of the primitive, not a reporting layer added afterwards. Every transition carries them, whoever or whatever caused it.
One history per record
Every transition records by, on, and changes. People, agents, and automations all write to the same trail, in order.
AI actions carry their reasoning
Each one records ai.reasoning, ai.sources, ai.confidence and ai.model on the action itself, not in a separate log.
The workflow decides what may happen
Permitted activities come from the state the work is in, not from whatever access the actor happens to hold. The same rule binds a person and an agent.
It stops and asks
Past a confidence threshold the agent pauses for a person rather than guessing. The question, the answer, and the score all stay on the record.
Actor parity
Same form, same validation, same permitted transition, whether a person, an AI agent, or an automation did the work. How it works →
Certified and patented
ISO/IEC 27001:2022 certified. Architecture protected by US Patent 11886836B2 and SG Patent 11202109454V. See the evidence →
Evidence is a query, not a reconstruction
Because the audit fields are native, the answers are already on the record: who acted, when, on what input, and for an AI action, on what reasoning and with what confidence. Your compliance team can map those fields to obligations such as EU AI Act Article 14, FINRA Rule 3110, the Colorado AI Act and HIPAA audit controls, instead of rebuilding the evidence from exports.
ISO/IEC 27001:2022
US 11886836B2
SG 11202109454V
Malaysia Digital status
Singapore SMEs: Inistate is an IMDA Pre-Approved Solution, so you may be eligible for up to 50% Productivity Solutions Grant support.
Start with one process. Prove it. Then roll out.
Nobody signs off a platform on a slide. Put one real process on Inistate, run it against your own controls, and take the audit trail it produces to the review. The rollout after that is configuration, not another project.
The company behind the platform
Founded in 2015, GNey Software turns complex business processes into working systems. Inistate is its flagship platform, and organisations run their operations on it today without long development cycles.
“Inistate’s flexibility and robustness are impressive where it covers our customized internal business process for Lavender’s fast-growing expansion.”Tam Yong Wen — Chief Executive Officer, Lavender Confectionery & Bakery
Bring one process to the briefing
Thirty minutes on your process, your controls, and what the record would have to show. No slideware.