Services Work Built Demos Pricing Contact Sign in See packages
What we've built

What we've built.

Four systems we designed, wrote and still operate. Every one of them is running right now — three you can open in a new tab and press buttons in. The numbers below are measured, not estimated.

See the four Bring us a project
Media pipeline · we run it

Furia — a film and music studio that runs itself

A character, a script, shots, a voice, a cut and a released track — produced by one pipeline instead of one editor. The hard part was never the picture: it was making the machine grade its own output and redo the takes that failed. Lip-sync is scored per shot against the voiced track and the shot is rewritten and re-rendered until it passes.

  • Own orchestrator over a three-GPU fleet — queueing, retries, node health
  • Per-shot scoring gates: lip-sync correlation, lag, vocal-gender check
  • Rights layer on every release: timestamped evidence, registry, territory rules

Stack Python · FastAPI · ComfyUI on 3 GPU nodes · SQLite · own queue and scoring

0.17 → 0.72lip-sync correlation after the pipeline rewrote its own prompts
3GPU nodes orchestrated from one control panel

Open the case → short film, album and the rights block

Storefront · live · we run it

Cruscy Music — songs sold direct, no label in the middle

A shop where a track is the product: listen, buy, download. Card and USDT both settle into the same order, so the buyer picks the rail and the seller sees one ledger. Installs as an app on a phone and keeps working with no signal.

  • Catalogue, player and checkout in one page — no cart, no funnel
  • Two payment rails into one order state machine
  • PWA: installable, offline-capable, its own tunnel and TLS

Stack Python · FastAPI · SQLite · own payment gateway · Cloudflare tunnel · PWA

31 KBfirst load of the storefront
0.26 sfull page response, measured from outside

Open music.cruscy.com → live — buy a song if you like one

E-commerce · live · client system

A clothing store built to survive its own traffic

A full storefront and the commerce platform behind it: catalogue, variants, stock, orders, payments and the admin the owner actually works in every day. Built as two services so the shop front stays fast while the back office does the heavy work.

  • Storefront and commerce API split — the shop never waits on admin queries
  • Payments, order lifecycle, scheduled jobs and a background worker
  • Server-rendered catalogue: it is indexable and it opens on a cheap phone

Stack Go commerce API · Next.js 16 storefront · Postgres · Redis · worker + scheduler

0.59 sfull storefront response, measured from outside
5services kept running as one system

Open the store → live commerce — real catalogue, real checkout

Infrastructure · internal · powers the rest

The studio — the conveyor the other three run on

Everything above shares one spine: a job goes in as a brief and comes out as a finished, rights-cleared asset, and every stage can be re-run on its own. The server only conducts — the heavy software lives on the machines that own the GPUs, so a node can die mid-render without taking the queue with it.

  • Brief → script → shots → voice → cut → rights, each stage restartable
  • Fleet keeper: nodes are checked, restarted and drained without a human
  • Own mail relay, own payment gateway, own tunnels — no rented middlemen

Stack Python · FastAPI · SQLite · Docker Compose · Cloudflare tunnels · Go mail relay

0third-party scripts, fonts or trackers on any site we ship
24/7everything on this page is running as you read it

How we work → no internal addresses — ask and we walk you through it

Yours would be the fifth.

Same people, same conveyor, same habit of measuring instead of promising.

Tell us what you need See packages