What we’re building
Most companies have integration sprawl — a workflow runs in Zapier, a script runs on Cron, an AI agent runs in some separate framework, and none of them know about each other. When something breaks, finding which surface owns the failure takes longer than fixing it.
RunMyCrew is a single platform where workflows, integrations, runs, and AI agents live in one graph, one logging pane, one permission model. Whether the run was triggered by a Gmail event, a webhook, a schedule, or a Crew AI agent, you see exactly what happened at every step and you can replay or edit it from the same editor.
Principles
- Open-source by default. The product is available on GitHub and ships as a single Docker Compose stack you can self-host. Hosted RunMyCrew is the same code with our operational hardening.
- Action over abstraction. The fastest path to running automation should not require learning a DSL, building a CI pipeline, or hiring an integration consultant.
- You own your data. No training on your prompts or content without opt-in, no advertising tracking, no sharing with brokers. Documented in the Privacy Policy.
- Production reality. Every workflow is observable end-to-end — payloads, retries, durations — so on-call engineers can debug the same way they would a microservice.
- Honest pricing.Self-host is free forever; the hosted plan charges only for runs and seats. No per-integration tax, no “upgrade for SSO” surprise on the enterprise tier.
Who’s behind it
RunMyCrew is founded by Bibek Timilsina, a software engineer based in Kathmandu, Nepal. The product evolved from years of hand-rolling integration glue for product teams and watching that glue rot. The platform is currently developed in the open; contributors are welcome.
How to reach us
See the contact page for the right inbox by topic. For everything else, GitHub Issues is the public bug tracker: github.com/bibektimilsina00/runmycrew/issues.