Liquid software: a new kind of computer for AI-native companies
Liquid software is the computing model where the apps and scripts you need don't ship pre-built — an AI agentic system writes them on the fly, deploys them, and runs them against the live state of your business. The Tony Stark / Jarvis framing is literal: a computer that builds the tool you need at the moment you need it, then dissolves it back into the pool.
osModa is the open-source platform that makes liquid software real. 10 daemons (9 Rust + 1 TS), 92 typed tools, 20 canonical skills, NixOS atomic rollback, hash-chained audit ledger, KEYD secrets vault. Apache-2.0 licensed. From $29/mo on a dedicated server, or self-host free. Below: how it works, why it's different from low-code, and what people are actually building.
TL;DR
- • Liquid software inverts SaaS: instead of fitting your work into someone's UI, the AI writes the UI for your work.
- • Powered by an agentic loop — plan → use tools → verify → stamp — running against typed primitives on a real machine.
- • osmoda makes it production-grade with NixOS atomic rollback, watchdog auto-restart, KEYD secrets vault, and a SHA-256 audit ledger.
- • Three safety layers (vault, policy gate, atomic rollback) keep the "AI writes anything" promise from becoming a security disaster.
- • Open source (Apache-2.0). Self-host free, or run managed at $29/mo. Live in 15 minutes.
1. Solid software vs. liquid software
Solid software is what we've had for fifty years. You ship it once; it does what it does. The user's job is to fit their work into the UI someone else designed. Liquid software is the inversion. The agent writes the UI for the work, on demand, and dissolves it when it's no longer needed.
| Dimension | Solid software (SaaS) | Liquid software (osmoda) |
|---|---|---|
| Who designs the UI | Vendor product team | Your AI agent, on demand |
| Who fits whom | You fit the tool | The tool fits you |
| Adding a feature | Submit a ticket | Tell the agent in English |
| Lifespan of an app | Years (hopefully) | Hours (often) |
| Source of truth | Vendor's database | Your own server |
| Customisation cost | Per-seat upgrade | Zero — it's just code |
| What happens at vendor's exit | Data export, lock-in | You keep running |
2. The agentic loop that makes liquid software real
Liquid software runs on a tight four-step loop. The same loop powers every piece of work — from drafting an email to scaffolding a SaaS app.
Plan
The agent reads your request, pulls relevant context from the archive, decides which specialists and tools it needs.
Use tools
Calls the typed tools — file ops, HTTP, exec, DB, payments, etc. Tool calls are typed, schema-checked, and logged.
Verify
Runs tests, checks outputs against expectations, retries on failure. Risky actions pause for your one-tap approval.
Stamp
Appends the action to a SHA-256 hash-chained ledger. Tamper-evident. Replayable. Forever.
3. Three safety layers that make "AI writes anything" tractable
The honest objection to liquid software is: "If the AI can write any code, what stops it from breaking everything?" Three layers, each non-optional:
KEYD vault — your keys can't leak
Secrets (API keys, wallet seeds, Stripe webhook secrets) live in a sandboxed daemon with no internet access of its own. Other agents can use them, but never see them. Allowlists + daily caps you can't unset. Even a misbehaving agent can't exfiltrate or spend past the cap.
Paper policy gate — irreversible actions wait for you
Anything irreversible — money out, prod deploy, mass-replying to customers — pauses for your one-tap approval. Spending caps stop runaway bills automatically. Bad changes roll back automatically. The agent doesn't hold the kill switch; you do.
NixOS atomic rollback — system state is reversible
Every system change is a new generation. If a deploy bricks the server, the previous generation is one boot away — even if the bad one knocked out SSH. The OS itself is the time-machine.
4. Liquid software in the wild — what people actually build
These are real examples that osmoda users have shipped. None were pre-built; the agent wrote them when asked.
Tip jar in 90 minutes
Domain bought, Stripe Connect wired, deployed to a live URL. From sketch on Sunday to charging on Monday.
Generative SEO machine
Finds keywords, writes pages, monitors ranks, ships fixes weekly. A page-a-week machine for the long tail.
3am incident responder
Server down → diagnose → fix → log to ledger. Pages you only when it can't fix it itself.
Trading copilot
Watches LP positions, alerts on liquidations, signs only with your tap via KEYD allowlist.
Daily P&L draft
Reconciles Stripe to invoices, files receipts, drafts the P&L every Monday morning, ready for your review.
Voice on walks
On-device Whisper + Piper. Talk to your studio on a walk; audio never leaves the box.
FAQ — liquid software
What is liquid software?
Liquid software is a computing model where the apps and scripts you need don't ship pre-built — an AI agentic system writes them on the fly against the live state of your business. It's the inversion of traditional SaaS, where you fit your work into someone else's UI. With liquid software, the UI fits your work because the agent generates it for you.
How is liquid software different from low-code or no-code platforms?
Low-code and no-code give you a visual editor where you click together pre-built blocks. The blocks are the limit. Liquid software has no blocks — the agent writes actual code, deploys actual services, and manages actual data on a real machine. If you can describe what you need, the agent builds it. Whatever you need, whenever you need it.
Is liquid software the same as 'agentic AI'?
Agentic AI is the engine. Liquid software is the user-facing experience. An agentic AI system that doesn't ship apps end-to-end is just chat. Liquid software is what happens when the agentic AI has root access to a real server, persistent memory, and the authority to write, deploy, and operate software on your behalf.
How does osmoda actually implement liquid software?
osmoda runs 10 daemons (9 Rust + 1 TS) on a dedicated NixOS server: agentd (runtime), watch (auto-restart), routines (scheduled jobs), teachd (skills/SKILL.md), mesh (P2P), voice (on-device STT/TTS), mcpd (MCP servers), egress (network policy), keyd (secrets vault), gateway (the OpenClaw chat surface). The AI agent has access to 92 typed tools and 20 canonical skills. When you ask for an app, the agent picks tools, writes code, deploys it, and routes it through the gateway — all audit-stamped to a hash-chained ledger.
Is liquid software safe? What stops the AI from breaking things?
Three layers. First, KEYD: secrets live in a sandboxed daemon with no internet access; allowlists and daily caps the AI cannot unset. Second, the policy gate (Paper agent): anything irreversible — money out, prod deploy, high-stakes reply — pauses for one-tap human approval. Third, NixOS atomic rollback: every system change is reversible in one command; if a deploy goes bad, the previous generation is one boot away.
Can I run liquid software offline / self-hosted?
Yes. The full osmoda engine is open source and Apache-2.0 licensed. Self-host on any Linux server — your laptop, a $5 VPS, your home server. The same agentic stack that runs the managed service runs locally. The only thing the managed service adds is a pre-provisioned dedicated server and turnkey billing.
What are some real examples of liquid software?
On osmoda today: a tip jar deployed in 90 minutes (domain bought, Stripe Connect wired, live URL); a generative SEO machine that writes pages, monitors ranks, and ships fixes weekly; a 3am incident responder that diagnoses outages and patches them before paging you; a trading copilot that watches positions and signs only with your one-tap approval. None of these were pre-built — the agent wrote them when asked.
Why call it 'liquid'?
Solid software is fixed — you ship it once, it does what it does. Liquid software flows around your needs. Ask for something different tomorrow, and the shape changes. The Tony Stark / Jarvis framing captures the same idea: a computer that builds the tool you need at the moment you need it, then puts it back in the pool.
Run liquid software on your own machine.
Apache-2.0 licensed. 10 daemons (9 Rust + 1 TS), 92 typed tools, hash-chained ledger. From $29/mo on a dedicated server, or self-host the engine free on any Linux box.
Last updated: May 2026