Umbrella Software Lab Send a brief

You had the idea yesterday. It goes live the day after tomorrow.

Umbrella Software Lab builds anything that runs on code: products, games, AI that takes work off your people, tools for your team, software for hardware nobody else will touch. You get a plan and a price the same day and click through a working build that week.

Send a briefSee prices

86 products taken to release in the last twelve months. Four games on Steam. A Telegram city builder live since June 2024, 19,048 commits deep.

What we fix

Bring the job other teams quoted for a quarter, or turned down. That one is ours.

Three weeks of calls before anyone writes a line of code.

We answer the same day with a plan, a fixed price and a date, and you click through the first build that week. Everything is in writing, so nothing waits for a meeting.

A support bot trained on 2,143 real tickets went from brief to working in one day.

You, 10:12We need a support bot that knows our 2,000 old tickets.

Umbrella, 11:40Plan, price and date attached. First version tonight.

Umbrella, 21:05It is live on staging. Ask it anything.

You, 21:30Wait, already?

The MVP is quoted at six months and a team of eight.

Auth, payments, admin, analytics, deploy. We build the whole thing in weeks, and real users are in it while others are still writing the spec.

A full 3D action game was playable on day one and had its release build on day 39. A SaaS is the smaller job.

Play it here
HELL IS FUEL: playable on day one, release build on day 39. The real game, in this page.

The code is old, in a language nobody hires for, on a machine nobody makes anymore.

Legacy systems, rare languages, firmware, protocols with no documentation. We read anything, fix anything and keep it running.

Spider-Man 2 went from the original Xbox to a $30 handheld in a day. Our action game runs natively on a PSP, a New 3DS and a Wii, and the whole run, two acts and both bosses, fits in a 384 KB cartridge for a 1988 Sega Mega Drive.

HELL IS FUEL on a PSP, a New 3DS and a Sega Mega DrivePlay the cartridge
The same game, native on a PSP, a New 3DS and a 384 KB cartridge for the Mega Drive.

The prototype works on the founder's laptop and nowhere else.

We take any AI-built or half-finished app to production: tests, CI, monitoring, releases you can ship on a Friday evening.

A Telegram game of ours ships to its players every day through staging and CI.

A Telegram game, updated for its players every day.

Your people spend half the day on the same tasks.

Support, approvals, reports, content, ads. Everything that repeats, we automate, and your people get their day back.

Every night a pipeline picks products from a catalogue, writes the SEO copy and queues them for Pinterest. A human only presses approve.

Promos our agents render from code, with sound on the beat. A fix is a re-render. Tap to watch.

You need a tool, and nobody sells the one you need.

Tell us what your team does by hand and we build the tool for it: image and sticker generators, AI picks for your catalogue, trailers rendered from code, ad managers with spend limits, bug reports an AI fixes on its own.

A MacBook trackpad turned into kitchen scales in one evening. A sticker pack goes from idea to installable in ten minutes.

flux-2-progpt-image-2ideogram-v4-qualitykrea-2-largegrok-imagine-image-2flux-2-max
One prompt, six image models, side by side.

86 products taken to release in the last twelve months.

60 of them went live within a week of their first commit. Sites, Mini Apps, bots, internal tools, console homebrew, two Steam games. Users or not, internal or external, every one of them shipped.

OctNovDecJanFebMarAprMayJunJulAugSepOct
Every square is one release, October 2025 to October 2026. Steam.

Code your team owns from day one

You get the product and everything needed to keep building it without us. Your product manager opens Claude Code or Codex, asks for a new page or feature, and the agent builds it the way the rest was built.

  • Clean code in your repositoryTyped, tested, with a deploy that runs from one command.
  • DocumentationA new developer is productive on day one.
  • RunbooksRelease, roll back, rotate keys, restore a backup. Written for the people on call.
  • Instructions for AI agentsAGENTS.md and skills for Claude Code and Codex: how this codebase is built, where things go, how to check the work. New features come out in the same style.

You can still call us. You won't have to.

your-product/ AGENTS.mdHow to work in this repo .claude/skills/add-page/New page, same patterns .claude/skills/release/Ship it, check it docs/architecture.mdWhat talks to what docs/runbooks/Release, rollback, keys src/Your product tests/Green before every merge README.mdRunning in ten minutes

Your product managerAdd a referral page that works like the pricing page.

AgentDone. Same layout, same components, tests pass, the preview is up.

Live right now

Players, payments and releases happening today. Every date and number here comes from git history, Steam and live links.

The support bot answering a customer in the site chatThe admin: a raw ticket thread turned into three answers for the bot
The live chat, and the admin where AI turns old tickets into answers. Names hidden.

A support desk that answers itself

For a 3D-model marketplace with thousands of customers.

2,143 real tickets distilled into 160 answers. The bot answers from them in the site chat; when it cannot help, the request lands with an operator by email. New tickets go back through an admin where AI turns them into answers, so the bot keeps learning. From brief to working: one day.

The daily drop: 250 models scored by AI, 36% approved automaticallyFocus review: one model with its AI-written pin copy, approve or reject
Tonight's drop: scored, written and queued by the pipeline. A person only approves.

A catalogue that markets itself

Pinterest on autopilot for a catalogue of 3D models.

Every night it picks models from the catalogue, an LLM scores them and writes the SEO copy, and the pins go out through RSS. The marketing team only presses approve.

City Holder

A city builder inside Telegram, live since June 2024.

A new season every few weeks, events, weather, AI buildings, payments in Stars. Under the one Mini App: game servers, an admin, analytics and a router on Rust. 19,048 commits across 33 repositories, every week since launch.

Week of 3 Jun 2024: 1 commitWeek of 10 Jun 2024: 16 commitsWeek of 17 Jun 2024: 20 commitsWeek of 24 Jun 2024: 86 commitsWeek of 1 Jul 2024: 123 commitsWeek of 8 Jul 2024: 259 commitsWeek of 15 Jul 2024: 561 commitsWeek of 22 Jul 2024: 507 commitsWeek of 29 Jul 2024: 243 commitsWeek of 5 Aug 2024: 283 commitsWeek of 12 Aug 2024: 203 commitsWeek of 19 Aug 2024: 320 commitsWeek of 26 Aug 2024: 235 commitsWeek of 2 Sep 2024: 301 commitsWeek of 9 Sep 2024: 365 commitsWeek of 16 Sep 2024: 225 commitsWeek of 23 Sep 2024: 295 commitsWeek of 30 Sep 2024: 328 commitsWeek of 7 Oct 2024: 277 commitsWeek of 14 Oct 2024: 136 commitsWeek of 21 Oct 2024: 204 commitsWeek of 28 Oct 2024: 147 commitsWeek of 4 Nov 2024: 167 commitsWeek of 11 Nov 2024: 176 commitsWeek of 18 Nov 2024: 249 commitsWeek of 25 Nov 2024: 215 commitsWeek of 2 Dec 2024: 268 commitsWeek of 9 Dec 2024: 238 commitsWeek of 16 Dec 2024: 207 commitsWeek of 23 Dec 2024: 309 commitsWeek of 30 Dec 2024: 242 commitsWeek of 6 Jan 2025: 109 commitsWeek of 13 Jan 2025: 198 commitsWeek of 20 Jan 2025: 130 commitsWeek of 27 Jan 2025: 143 commitsWeek of 3 Feb 2025: 511 commitsWeek of 10 Feb 2025: 135 commitsWeek of 17 Feb 2025: 234 commitsWeek of 24 Feb 2025: 223 commitsWeek of 3 Mar 2025: 213 commitsWeek of 10 Mar 2025: 147 commitsWeek of 17 Mar 2025: 155 commitsWeek of 24 Mar 2025: 115 commitsWeek of 31 Mar 2025: 98 commitsWeek of 7 Apr 2025: 154 commitsWeek of 14 Apr 2025: 223 commitsWeek of 21 Apr 2025: 73 commitsWeek of 28 Apr 2025: 88 commitsWeek of 5 May 2025: 62 commitsWeek of 12 May 2025: 42 commitsWeek of 19 May 2025: 36 commitsWeek of 26 May 2025: 73 commitsWeek of 2 Jun 2025: 44 commitsWeek of 9 Jun 2025: 52 commitsWeek of 16 Jun 2025: 20 commitsWeek of 23 Jun 2025: 38 commitsWeek of 30 Jun 2025: 51 commitsWeek of 7 Jul 2025: 47 commitsWeek of 14 Jul 2025: 143 commitsWeek of 21 Jul 2025: 69 commitsWeek of 28 Jul 2025: 71 commitsWeek of 4 Aug 2025: 96 commitsWeek of 11 Aug 2025: 191 commitsWeek of 18 Aug 2025: 99 commitsWeek of 25 Aug 2025: 296 commitsWeek of 1 Sep 2025: 210 commitsWeek of 8 Sep 2025: 100 commitsWeek of 15 Sep 2025: 197 commitsWeek of 22 Sep 2025: 188 commitsWeek of 29 Sep 2025: 82 commitsWeek of 6 Oct 2025: 74 commitsWeek of 13 Oct 2025: 41 commitsWeek of 20 Oct 2025: 99 commitsWeek of 27 Oct 2025: 125 commitsWeek of 3 Nov 2025: 150 commitsWeek of 10 Nov 2025: 94 commitsWeek of 17 Nov 2025: 113 commitsWeek of 24 Nov 2025: 71 commitsWeek of 1 Dec 2025: 55 commitsWeek of 8 Dec 2025: 84 commitsWeek of 15 Dec 2025: 145 commitsWeek of 22 Dec 2025: 271 commitsWeek of 29 Dec 2025: 53 commitsWeek of 5 Jan 2026: 74 commitsWeek of 12 Jan 2026: 114 commitsWeek of 19 Jan 2026: 173 commitsWeek of 26 Jan 2026: 70 commitsWeek of 2 Feb 2026: 55 commitsWeek of 9 Feb 2026: 38 commitsWeek of 16 Feb 2026: 63 commitsWeek of 23 Feb 2026: 55 commitsWeek of 2 Mar 2026: 48 commitsWeek of 9 Mar 2026: 42 commitsWeek of 16 Mar 2026: 112 commitsWeek of 23 Mar 2026: 240 commitsWeek of 30 Mar 2026: 62 commitsWeek of 6 Apr 2026: 83 commitsWeek of 13 Apr 2026: 156 commitsWeek of 20 Apr 2026: 35 commitsWeek of 27 Apr 2026: 104 commitsWeek of 4 May 2026: 126 commitsWeek of 11 May 2026: 105 commitsWeek of 18 May 2026: 237 commitsWeek of 25 May 2026: 357 commitsWeek of 1 Jun 2026: 605 commitsWeek of 8 Jun 2026: 308 commitsWeek of 15 Jun 2026: 109 commitsWeek of 22 Jun 2026: 39 commitsWeek of 29 Jun 2026: 31 commitsWeek of 6 Jul 2026: 36 commitsWeek of 13 Jul 2026: 78 commitsWeek of 20 Jul 2026: 232 commitsWeek of 27 Jul 2026: 194 commitsWeek of 3 Aug 2026: 203 commitsWeek of 10 Aug 2026: 200 commitsWeek of 17 Aug 2026: 74 commitsWeek of 24 Aug 2026: 24 commitsWeek of 31 Aug 2026: 3 commitsWeek of 7 Sep 2026: 25 commitsWeek of 14 Sep 2026: 17 commitsWeek of 21 Sep 2026: 59 commitsWeek of 28 Sep 2026: 238 commitsWeek of 5 Oct 2026: 405 commitsWeek of 12 Oct 2026: 31 commitsWeek of 19 Oct 2026: 51 commits
Commits per week since launch. The red bar is this week.
A Lobsters characterLobsters1,254 NFT characters on TON. Each one has a soul, a memory of its owner and a Telegram bot of its own.A web app, a Mini App, an MCP server, an arena and a pipeline that dresses 10,000 more. About 273 bots talk to their owners right now.Open the caseBAASA game layer for banks.Every client gets an island, and every card payment builds something on it. People open the bank app when there is nothing to pay.Open the case

How it goes

You write
Any language, any format: a paragraph, a voice note, a screenshot, a forwarded chat. Our own intake tool turns it into a brief. We reply the same day with a plan, a fixed price and a date.
You see it working
Each stage ends with something you can open and use. You pay stage by stage.
You never chase us
No standing calls. Every decision stays in one written thread, and the build moves every day.
You keep it
Code, docs and agent instructions are yours. Your team carries on, or we stay on support.
Nothing is off the table
Banks, games, Telegram, AI, a printer protocol, a console from 1988. If it runs on code, we take it.

Prices

Fixed scope, fixed price, paid stage by stage. Not sure where to start? Start with a discovery sprint; its cost comes off the project.

Start

  • Discovery sprint$750–1,5003 to 5 days: a prototype, an audit or a plan. The cost comes off the project.

Build

  • MVP or SaaS$8–20kFrom the first screen to paying users, in weeks.
  • Telegram Mini App$6–15kA working app with a backend, payments and an admin.
  • Game prototype$4–10kThe core loop on the target platform, playtested.
  • Multiplayer$6–15kAuthoritative server, matchmaking, netcode that holds up.

Fix and finish

  • Prototype to production$3–10kAn AI-built or half-done app made safe, fast and shippable.
  • Legacy, rare stacks, hardware$3–10kOld code, odd languages, firmware, protocols nobody documented.
  • Code audit$800–1,500Your codebase read end to end, with a written plan.

Automate

  • AI support, agents, pipelines$3–8kWired into the tools your people already use.
  • A tool for your team$2–6kGenerators, dashboards, kits for your agents.

Launch

  • Steam release$2–4kStore page, builds, Steam Input, the release checklist.
  • Pitch demo or landing$2–5kA page that sells the idea before the product exists.
  • Trailer$1.5–3kGame trailers, ads and teasers.

After launch

  • Support and live-ops$300–1,000/moFixes, updates, events and someone on call.

Send a brief

Any language, any format. Tap a few chips and say it your way: you get a plan, a price and a date back the same day.

What do you need?
Budget
When