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 — most a single Cloudflare Worker, the rest managed integrations wired in as standard — 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.
Org email and accounts on Google Workspace for Nonprofits — provisioned and managed by the agent in Slack through an admin MCP, no console to learn.
The public site publishes to the web and syndicates to your social channels in one step, so announcements reach members and followers together.
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.
A tribe's record can't live or die with a database that corrupts or a vendor that folds. So orgware keeps it the way serious archives are kept — tracked primarily in Git, version by version, then replicated into cold storage nobody can quietly overwrite.
Every record and its source scan lives in Git — an archival-grade way to manage data at scale, where each change is an immutable, attributed commit, the whole history stays recoverable, and every clone is a complete redundant copy. Nothing is ever silently overwritten or lost to a bad edit.
Point-in-time recovery across a rolling 30-day window, plus nightly encrypted exports — so the live database can be rebuilt to any recent moment, not just the last snapshot. The most sensitive data is encrypted at every hop, its key held offline.
Encrypted long-term archives replicated to Backblaze B2 and Amazon S3. Every piece of tribal data, held off-platform, hardened against hardware failure, vendor failure, and human error alike — all of it for less than five dollars a month.
Indexed and searchable back to the early 1990s — and no single point of loss anywhere in the chain.
Recognition, self-governance, and continuity all rest on the same foundation: records a government can stand behind. Scattered across binders, inboxes, and mutable cloud docs, they get waved off as informal. An auditable, independently-verified corpus — every resolution, election, and appointment, each anchored to a primary source — is the difference between a story and a standing.
orgware doesn't just store the record — it makes it defensible: provenance on every document, independent verification, and a transparent trail of how ambiguous records were adjudicated instead of silently flattened. The kind of record a reviewer, a court, or a federal panel can't hand-wave.
The people who own the data operate and extend the platform by describing what they need — in their own Slack, in plain English. A resident agent triages every request against the live code, batches the work, and ships it, often the same day. Features and fixes don't wait for a quarterly release — they arrive in a steady stream.
Ember — the tribe's resident agent — triages that against the live code and the fix ships to production the same day. That's not a highlight reel; it's the ordinary cadence. In the run-up to launch the Roll Book alone grew from a flat list into a full editor — self-service fields, faceted filters, bulk actions, a provenance trail, a live cost console — request by request, in Slack.
Features and bug reports come in the same way — through Slack — and get triaged, batched, and shipped rapidly, no ticket queue. And because every instance runs orgware, the platform underneath keeps getting better on its own cadence: new capabilities and hardening arrive as regular updates, with no re-platform.
No admin console to learn, no queue to wait in. If you can describe it in a sentence — a new feature or a bug you spotted — you can ask for it. The conversation is the interface.
Requests are triaged against the live code, batched, and shipped — often same-day. Always-on agents (OpenClaw) and Claude do the legwork; a human signs off. Nothing reaches production unsupervised.
orgware itself ships continuous improvements — every instance inherits new capabilities and security hardening without a migration or a re-platform project.
orgware is what the composable, edge-native, agentically-built stack produces taken all the way to a shipped product. It's the successor to the PHP/Java monolith — the same composable-plus-edge-delivery model the big platforms now sell as their premium future, on open foundations, with no license fee and no lock-in. For any team — a heritage brand, a member organization, an institution — carrying decades of data on a platform it has outgrown, it's a working reference for where delivery is heading.
The successor to the PHP/Java monolith — composable, edge-delivered, open, and yours. Rivaling the builder and edge-delivery capabilities the incumbents sell as premium, without the license or the lock-in.The path the platform providers would rather you didn't consider.
The agentic layer runs on whatever you already pay for — Claude Code, Codex, GitHub Copilot, or any model API. Point it at a flat-rate coding subscription and the whole build-and-operate layer runs from about $20 a month. Hosting stays at $0. No per-seat licensing, no metered surprise, no vendor holding the meter.
The pitch is the proof. Everything on this page runs on the stack it describes. And because the platform is built to be legible to agents — small services, a single access rule, provenance by default — a coding agent gets productive in minutes and carries work from triage all the way to production. Higher data fidelity, more throughput, 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.
If you're a tribe or a nonprofit that wants to learn more, reach out. The toolkit is free and open source — self-host it, or let us run it for you fairly and transparently, with full data portability and fit-for-purpose enterprise MCPs and models. Hands-on help when you want it. Either way it's yours: ownership and control, never a vendor's lease.
Built and maintained by Doug Hatcher — an enterprise architect at one of the world's leading digital agencies, a founding member of one of the most influential tribes in the state, with a lifelong commitment to excellence and to putting enterprise-grade software within reach of anyone who needs it.