X&CO Two products · one studio

X&CO

The studio behind TestKit and TaleUs. Two focused products, built and run by the people who needed them.

TestKit · testkit.app TaleUs · taleus.app
Move your cursor through the field
TestKit · testkit.app

Testing that finally feels organized.

Built by QA, for QA. TestKit drafts cases from your Jira issues, pulls results straight from CI, spots the flaky ones, and gives the release a clear go or no-go.

  • AI test cases from stories and Jira issuesPlan
  • Zero-setup CI: JUnit, Playwright, Cypress, Jest, pytestRun
  • Flaky detection with automatic quarantineStabilize
  • Evidence on every run: screenshots, logs, recordingsProve
  • Go/no-go dashboards and public share linksRelease
Open testkit.app →
TaleUs · taleus.app

Co-write a story online, together, live.

A shared page for stories. Start a tale, invite anyone, and write it forward in real time, cursor beside cursor. Then read it back as one voice.

  • Real-time co-writing with live collaborator cursorsWrite
  • Read and write in one continuous pageRead
  • Public or private stories, shared by linkShare
  • A library of finished tales from the communityDiscover
Open taleus.app →
A note from the person who built this
I'd rather run two products I actually care about than a dozen I don't. Everything below is because of that.
Why one job

I build one thing, and build it well

TestKit exists to answer one question: are we ready to ship? TaleUs exists to answer another: what happens next? I don't bolt features onto either just because a trend says to.

Why these two

I build what I'd actually use

Both started because the alternatives frustrated me enough to fix them myself. If a feature doesn't make sense to the person actually testing, or actually writing, it doesn't ship.

How I run it

I answer to customers, not investors

No venture rounds, no growth-at-all-costs roadmap. Pricing stays honest, free tiers stay free, and I build things meant to run for years, not to flip.