Automation as code, with the hard parts already wired up.

Everything should be code, including automation

Business automation is just software. It should be written in code.

In the days of yore, non-coders had to build automations using poorly-designed interfaces in tools like Zapier and Make.

Today, LLMs do our bidding. We've created an automation framework using a language they love to write: TypeScript. Moreover, once your automation is code, it can be versioned, tested, and deployed like code. For example, you can upload to GitHub to track changes and manage rollbacks.

Backend tools are not enough

Supabase and Convex are great for building products. Temporal is great for durable execution. But business automation has a different pile of boring problems.

You need triggers. You need OAuth. You need API keys. You need common actions for Gmail, Slack, CRMs, ticketing systems, and the rest of the business software swamp. You need event routing and utilities before the actual workflow can even begin.

OpKitty brings those pieces with it. Advanced orchestration plus pre-built trigger and integration infrastructure. That's the product.

The plumbing is the product

The hard part of automation is rarely the happy-path function. The hard part is getting the trigger, credentials, retries, state, long-running execution, and destination systems to behave at the same time.

OpKitty handles that scaffolding so the workflow can stay lightweight. You write the automation. OpKitty deals with the machinery around it.