Idunworks Issue #01
Issue #01 · The platform layer Oct 2026

Ifanymonkey can build a web app with AI, then why don't you?

Monkey says… Ook. I shipped three tenants before lunch.
A pink punk chimp in a gold crown, squatting on a keyboard, on a torn sunburst poster
I can has platform? Monkey see, monkey ship

Idun is the platform layer under the app: a multi-tenant CMS, AI helpers that know your content, and deploys that don't wake anyone at 03:14. You bring the idea. We bring the boring bits that keep it running.

T-shirts for webd peeple Print yours in the T-lab → No time for fake pages
Build platformsNot pagesI can has zero downtimeMuch tenant. Very deploy. WowMonkey see, monkey shipOne MakefileBuild platformsNot pagesI can has zero downtimeMuch tenant. Very deploy. WowMonkey see, monkey shipOne Makefile

On the newsstand

Three stories from the engine room. Tap a cover to read the blurb.

It came from a single codebase.
Multi-tenant & plugins

One repo powers many frontends: shared components, per-site themes and a plugin system that won’t break at 03:14 in the morning.

A new brand is an env file and a theme folder, not a fork.

Read on: Multi-tenant architecture explained →
Smart workflows. Real guardrails.
AI agents, smart workflows

AI-assisted code generation, autonomous agents and guardrails that survive contact with real users and production data.

The helpers read your content model, so they draft pages that actually fit.

Read on: Complex automation →
Your legacy stack, tamed.
Docker, deploys, zero downtime

Green/blue deployments, port isolation, volume management and the battle-tested Makefile that ties it all together.

Every site gets its own port offset, its own database and the same boring, reliable ship command.

Read on: The staging environment is your best business decision →

At this pointin my stack, I'vestopped pretending.

I'm not a hot mess.

I'm the full platform package

  • Included: Multi-tenant, one codebase
  • Included: Blue/green deploys
  • Included: AI that reads the docs
  • Included: One Makefile to rule them
  • Not included: Excuses

And not particularly sorry about it.

House rules

Monkey says: cut out & keep
  1. 01 Ship small. Ship often. Ship on a Tuesday.
  2. 02 Move fast and break things.
    Move fast and break nothing.
  3. 03 Own your data. Own your stack. Own your weekends.
  4. 04 Boring infrastructure. Wild frontends.
  5. 05 I can has deploy on Friday?
    You can has deploy any day. It is blue/green.
  6. 06 Rewrite it in a new framework.
    Fix the thing that is actually broken.

Classifieds

Amazing offers!

Meanwhile, in the engine room…

Dispatches

I can has blog?

Stop scrolling. Start shipping.

Tell us what you want to build. We answer every message ourselves, no bots in the inbox.

Let's talk → U can has meeting. No slides.
No monkeys were harmed