01
Small surface area, by choice.
Two products, deliberately. A studio that runs two products well can be wrong in two directions; one that runs twenty can be wrong in twenty.
Abyssinia Labs · Est. 2026
An independent studio for software with weight.
We work on a small number of products at a time and ship them with the patience of a long-running practice. Two live here today — one for the people building agentic systems, one for filmmakers who want AI in the margin, not the byline.
I · Two products under one roof
Built for two crafts. Run from the same workbench.
Open betaDeveloper infrastructure
MCPCloud.sh
Server factory and skill studio for agentic infrastructure.
Import an API spec, ship a typed MCP server to a global edge runtime, and author the skills that orchestrate it — all in one workspace. Generated code that still feels owned; secrets that never land in source.
For developers and platform teams shipping agents.Visit mcpcloud.sh
Vol. I · WaitlistCreative production
Crafty Studio
An AI-assisted production studio for filmmakers.
Eight stages of filmmaking — idea to publishing — with context that accumulates as you move. Crafty sits in the margin and proposes; the filmmaker stamps, rejects, or revises. Every block of work is signed.
For filmmakers, screenwriters, and creative directors.Visit mycrafty.studio
II · Operating principles
Three commitments, signed by the studio.
02
One studio, two disciplines.
Developer infrastructure and creative practice draw on the same craft — clarity, restraint, taste. Both products are first-class; neither is a side project.
03
Owned, not anonymous.
Generated code is yours to read, edit, and export. Authored output carries the byline of the person who approves it. We don’t ship work without a name on it.
III · The studio
What we believe.
The work we ship is small in count and dense in surface area. We design for the person who’ll be using the product on a Tuesday — not the buyer who sees the demo on a Monday. Marketing pages cool down; the tool sits with you for years. Every decision we make on the landing page must hold up in the daily-use surface behind it.
We separate generated from authored, and treat both with respect. Code our tools write should still feel owned by the people who maintain it. Work our agents draft should always carry the byline of the person who approves it. Anonymous output is not a feature.
IV · Contact
Working on something adjacent?
We’re a small team and we read every note. Press, partnerships, or a thoughtful product question — write to us directly.