X&CO Three products · one studio

X&CO

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

Move your cursor through the field
TestKit logoTestKit · 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 logoTaleUs · 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 →
Stockfiti logoStockfiti · stockfiti.com

Don't just say it, spray it.

Stock and crypto sentiment from the crowd. Pick any stock, ETF or coin, write your take in 100 characters, and it goes up as graffiti on a public wall the whole market can see.

  • Search any ticker or company and open its wallFind
  • Tag your take in 100 characters, bull or bearTag
  • Dozens of graffiti lettering styles and paintsStyle
  • A live wall of what retail investors are sayingRead
Open stockfiti.com →
A note from the person who built this
I'd rather run three 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? Stockfiti asks a third: what does the crowd really think? I don't bolt features onto any of them just because a trend says to.

Why these three

I build what I'd actually use

Each one started because the alternatives frustrated me enough to fix them myself. If a feature doesn't make sense to the person actually testing, writing, or investing, 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.