About Raiken
We're building tools to make end-to-end testing faster, more reliable, and less painful for engineering teams.
The problem we're solving
E2E tests are essential, but they're also a constant source of friction. Writing them takes time. Maintaining them takes more. And when they break, often due to minor UI changes, teams either waste hours debugging or disable them entirely.
The result is a gap between "we should have tests" and "we actually do." QA becomes a bottleneck, coverage stays low, and regressions slip through.
We built Raiken to close that gap.
Our approach
Raiken is a CLI tool that generates Playwright tests from plain English descriptions. But unlike generic AI code generators, Raiken understands your project first. It indexes your codebase, captures your actual UI, and uses that context to produce tests that work.
Everything runs locally. Your code stays on your machine. The only thing sent to the AI is the minimal context needed for generation.
We believe testing tools should be fast to set up, easy to use, and respect your privacy by default.
What's next
Today, Raiken handles single-page DOM capture and test generation. We're actively building:
- • Multi-page flow capture with AI-assisted navigation
- • Integration with Jira and GitHub to keep tests aligned with requirements
- • A collaborative test graph for teams to build and share test flows
- • Auth helpers to capture session state for protected pages
Our goal is to make Raiken the fastest path from "we need tests" to "we have them."
Get in touch
We're a small team and we love hearing from users. Whether you have feedback, feature requests, or just want to chat about testing, reach out.