orgware gives a tribe, a nation, or a member organization the software a large institution has — a secure member portal, an authoritative record, transparent operations — built on the edge, running for a few dollars a month, with no servers to babysit.
Live from the waccamaw.org instance · updating…
orgware is composed of small, independent pieces — each a single Cloudflare Worker — so any one can fail or be replaced without taking down the rest. The public, visitor-facing site stays exactly where it is; orgware only takes over the moment someone signs in.
Passwordless sign-in, the verifiable knowledge library, per-member API keys, the roll book, and a live cost console.
A role-scoped contact directory for leadership and the public contact forms — stateful, no third-party form service.
Recovered and ongoing minutes and transcripts, members-only until reviewed, with an Apple-compatible podcast feed.
The same authoritative record exposed to AI assistants over a standard MCP endpoint — under the exact same access rules.
The same address shows different things to different people.
The visitor site, the museum, public records and minutes.
Adds the portal, the cleared record library, and a personal API key.
Adds the full record, the roll book, the directory, and the cost console.
The guarantee: nothing gated is ever sent to someone who hasn't signed in. Private pages aren't hidden with CSS — they're rendered by an authenticated Worker that returns nothing until it has verified your session.
◆ The first instance · in production
901 enrolled members with self-service records. A governing record reaching back to 1994 — 108 resolutions, the constitution, offices, and decisions, each traceable to a primary-source scan. A recovered meeting archive. A record that answers to AI assistants. All of it edge-hosted, and this month it cost $0 to run.
It is a working proof that a small nation can hold institutional-grade software — a member portal, a verifiable record, honest books — without an institutional budget, a server room, or a vendor contract that owns the door.
orgware runs entirely on Cloudflare's edge. No servers to patch, no virtual machines, no monthly hosting bill beyond usage. Each part runs close to whoever's asking, backed by Cloudflare's own database, storage, and key-value store.
Owning your software usually still means filing tickets and waiting on a vendor. orgware closes that gap: the people who own the data operate and extend the platform by describing what they need — in plain language, in their own Slack. A resident agent is already in the room.
The message lands in Slack, where Ember — the tribe's resident agent — triages it against the live code the moment it's posted. Within the day the gap is traced across three repositories, a database migration is applied to production, and both the backend and the website ship — a new "core member" flag with a checkbox, a filter, and a roster badge, live on waccamaw.org.
Ember reads the same repositories and services the platform runs on. It answers questions, makes the safe fixes itself, and files the rest — as itself, in the open, never on anyone's behalf.
The agent layer does the legwork — always-on agents (OpenClaw) and Claude for the building — but it never merges, force-pushes, or deploys on its own. A person signs off. Nothing reaches production unsupervised.
No separate admin console to learn, no queue to wait in. If you can describe it in a sentence, you can ask for it. The conversation is the interface.
orgware is what the composable, edge-native, agentically-built stack produces when you take it all the way to a shipped product. For teams moving real workloads off monolithic platforms, it's a working reference for a different way to deliver.
The pitch is the proof. Everything on this page — the portal, the record, the AI endpoint, the live numbers above, this page itself — runs on the stack it describes. It's a template for rapid, deeply-customized delivery on infrastructure that doesn't bill you for existing.
hatcher.ltd owns the software.
You own your record.
orgware is a product. Your organization's data, decisions, and history are yours — held in your own repositories, under your own clearance, on infrastructure in your name. The platform doesn't belong to any officer, any term, or any faction, and it doesn't wobble when leadership changes. It's software with an owner and a record with a home, kept deliberately apart.
Another nation, a member association, or an implementation team looking for a better stack — start a conversation.