Notes on automation people have to trust.
Mechanism over opinion. Every post says what the product does today, and says roadmap when it is roadmap.
- Platform5 min read
What 1,075 integrations actually counts: providers, operations and connections
What 1,075 providers means on OCNORA: how providers, operations and triggers are counted, where cloud services fit, and what one connection drives.
- Agents5 min read
How to decide which support actions an AI agent may take alone
Classify the ticket, fence the agent’s tools, treat confidence as a routing input and put a person, a timeout and a fallback in front of the risky step.
- Build5 min read
How a bug report becomes a reviewed change on your own runner
How OCNORA Task Runs take a bug report through intake, a Git worktree on your runner, your own checks, blocked states and a person’s review before anything merges.
- Run5 min read
How to move CSV data into a SQL table and know the transfer was correct
Map the columns, check the types, key the rows, batch and retry the writes, then compare counts and checksums on both sides and give rollback to a named owner.
- Build5 min read
What to check when you import an n8n workflow into OCNORA
Credentials, expressions, branches, placeholder steps and Code nodes: what the n8n importer carries across, what it leaves to you, and how to run the first test.
- Run5 min read
Plan an application migration as a series of workflows
Inventory, dependency checks, tests, transfer, validation, a cutover gate and a rollback owner: what orchestration does in a migration, and what it does not.
- Run6 min read
Run a cloud operations workflow across services, with credentials and an approval
One scoped cloud operations example: the AWS permissions it needs, request limits, the error path and a person’s approval before the workflow scales anything.
- Platform6 min read
Embed workflow automation in your product: where identity, tenants and support sit
Where identity and tenant boundaries sit when you embed OCNORA: the token handoff, roles, connections, tenant setup, support and who runs the installation.
- Govern4 min read
How to test a workflow before it touches anything real
Static validation, a dry run against real config with side effects held back, then a first live run on one record. A practical order for shipping automations safely.
- Agents5 min read
How to keep an AI agent’s spending close to the number you set
A retry loop, a huge tool result or a growing prompt can turn one agent into a runaway bill. Here’s how per-tenant budgets and a circuit breaker limit it.
- Govern5 min read
How much a dry run actually proves before you trust it live
A dry run executes your workflow with side effects suppressed and shows each step’s output shape. That shows the path resolves, not that the result is right.
Reading about it is the slow way.
Install a template, run it once, and see the audit trail it leaves behind.