Custom backends
Typed, tested services in Node, Python, Go, or Rust. Auth, billing, search, queues, AI pipelines - written to fit your domain, not a template.
Monarch TCH builds software that balances engineering discipline with the lightness of craft. Three strands - Technology, Creating, History - woven into every product we ship.
A flock of engineers, designers, and strays who fell in love with the tinker. We build weird software on purpose - and ship it anyway.
Technology, broadly. From Postgres queues and typed services to embedded firmware on microcontrollers, desktop and mobile apps, AI-powered systems. Whatever the problem needs - that's what we ship.
We touch metal. We poke microcontrollers. We make AI hallucinate on purpose. The bench is loud and almost always smells like solder.
The workshop. Prototyping as a habit, not a phase. We sketch in code, test with users on day three, and ship small weekly increments.
Sketch on day zero. Demo on day three. Throwaway prototypes that secretly become the product. The throwaway is the point.
The long view. Every decision is documented, reversible, and told as a story - so the team that inherits this code can read it like a letter.
Every project leaves a scar. Every commit gets remembered. Someone will read this at 2am - we want them to smile.
Possibility isn't the bottleneck. Time and scope are. Tell us the brief, the deadline, and the budget - we'll come back with a plan, not a maybe.
Tell us when →We build the backbone and the front door - APIs, ERPs, schedulers, integrations, and the marketing sites, mobile apps, and dashboards that sit on top of them. Both halves matter. Most clients hire us for the half no one sees.
Typed, tested services in Node, Python, Go, or Rust. Auth, billing, search, queues, AI pipelines - written to fit your domain, not a template.
REST, GraphQL, tidy RPC. Stripe, CRMs, AI providers, legacy systems. ETL, schemas, scheduled pipelines - with retries, observability, and migrations you can actually run.
The bespoke admin dashboards, multi-tenant SaaS, and internal systems companies actually run on. Where the real money lives, even if no one screenshots it.
Public-facing sites, headless CMS (Sanity, Payload, custom), landing pages, blogs. The part marketing fights about; the part engineering keeps alive.
iOS, Android, or cross-platform with React Native. Offline sync, native integrations, the lot. We pick native vs cross-platform based on what the product actually needs.
The work that keeps a product up at 3am. Schedulers, queues, migrations, monitoring - the bits no customer ever sees. Less photogenic than a landing page. Far more load-bearing.
We pick what fits the problem - not what's trendy, not what's familiar. Below, a snapshot of what tends to live on our bench.
…and whatever else a project quietly needs. The list shifts every year - that's the point.
Most of our work is the backbone of someone else's product - APIs, schedulers, internal tools, the things that don't make good marketing screenshots but quietly run the business. So instead of case studies, here are the teams we currently ship for, in plain text.

Brief, research, and a written hypothesis. Two weeks, fixed fee.

Prototypes in the hands of users. We argue with the evidence, not each other.

Production build in small, shippable slices. Weekly demos, monthly retros.

Handover with a runbook, a story, and a future self-maintainable system.