How it works
From a sentence to something that runs.
What you build becomes a durable business object. It runs, leaves evidence, and stays open to change.
Your AI is the way in. Cynap is what keeps it working.
Provider accounts stay with their providers. Cynap supplies the shared workspace, permissions, business context, and runtime.
AI-provider charges are separate and paid by you.
You describe it
Explain the job in plain language. The authoring environment asks about what is missing instead of guessing.
A weekly customer-risk reviewIntent made specificIt gets built
Codex or Claude Code turns the instruction into a real object in your workspace: an automation, report, view, or integration.
Customer risk reviewReady for your approvalIt runs
Cynap runs it on a schedule or when something changes in a system you already use.
Every Friday at 08:00Working across your recordsYou can see what it did
A run leaves an organisation-scoped record of its steps and, where a browser was used, what it saw.
Run completedOutcome and usage recordedIt starts telling you things
As the shared picture fills in, Cynap can raise what it notices instead of waiting for another request.
One customer changed patternRaised for attentionYou decide what happens next
Change it, narrow what it can touch, or switch it off. A person remains responsible wherever money moves.
Review the prepared follow-upDecision remains yours
Your data, your choice.
Point Cynap at the systems you already use, or make Cynap the source of truth. Both are supported. The choice remains yours.
Or ask, and it arrives built.
Request a build and it comes back as the same kind of object in the same workspace. You simply did not author it.
Pick the one job you want off your desk.
Building does not consume Cynap Credits. AI-provider charges are separate. Nothing you build is ever deleted.