A DAO's constitution is its contracts, but its working life runs on software somebody else operates: a voting front end, a forum, a member workspace, a payments app, a badge issuer, an analytics dashboard. Those tools are chosen once, wired into the way the organization actually works, and then almost never revisited. DAO tooling discontinuity is what happens when one of them stops existing.
The industry treats this as an operational annoyance. It is closer to a governance problem, for three reasons this page works through: the damage depends entirely on what the tool was holding, not on how important it felt; the signals people use to check whether a tool is still alive are unreliable in specific and predictable ways; and unlike a service provider, a SaaS dependency is usually adopted below the threshold that would ever put it to a vote, so when it fails there is no owner and no process.
Between February and August 2026 this wiki kept a queue of DAO tooling products it intended to write up. Each was, at the time it was added, a going concern with a product site and users. On 5 August 2026 all seven were checked directly before any page was written. Six were gone, parked, or no longer in the category.
| Tool | What it did | State on 5 Aug 2026 |
|---|---|---|
| Llama | Treasury and governance framework | Gone. llama.xyz returns no DNS A record at all, and llamaxyz/llama is flagged archived with its last push on 16 August 2024. |
| Otterspace | Non-transferable membership badges | Gone. otterspace.xyz still resolves to Netlify addresses but the TLS handshake fails, and the otterspace-xyz contracts repository is a 404. |
| Utopia Labs | DAO payments and payroll | Gone, and the domain has since changed hands. On 5 August 2026 utopialabs.com answered 200 with a 734-byte holding page: a title, a webfont link, and an empty root element. Re-checked 12 September 2026 it answers 200 with 7,677 bytes of a different business – a page titled “Atlas” selling an aircraft (“Introducing Atlas 1.2”, flight time, 270 km/h top speed, 0 m runway, “Visit our hangar”), served off Vercel, with no occurrence of “Utopia”, “DAO”, “payments” or “payroll” anywhere in the document. app.utopialabs.com still has no DNS A record. |
| CharmVerse | DAO workspace, proposals and roles | Product gone. charmverse.io serves a domain-parking lander, app.charmverse.io has no DNS A record, and the repository is not archived, last pushed 18 October 2025. Re-checked 12 September 2026: the apex answers 200 with 114 bytes – a bare window.onload that sends the browser to /lander – so the lander is reachable only by executing JavaScript, and a plain fetch never sees it. |
| Syndicate | Investment-club framework | Pivoted out of the category. syndicate.io now sells "the infrastructure to infinitely scale Ethereum" and lists an exchange-traded token. The investment-club product is not part of it. |
| Metropolis (ex-Orca Protocol) | Membership pods over a Safe | Pivoted out of the category. metropolis.space answers 200 with a live site for deployment tooling and a Solidity podcast, not a pods product. The contracts repository does not 404: orcaprotocol/contracts 301s to 0xmetropolis/contracts, last pushed March 2023, in an organisation that now ships token-launch tooling. Re-checked 26 August 2026, when the old marketing domain metropolis.xyz was also found parked and listed for sale. |
| Den | Multisig operations over Safe | Alive at onchainden.com. Note that den.xyz, the domain people assume, is parked for sale and is a different thing. |
Treat that as one dated observation, not a survival rate: it is a convenience sample of seven, assembled because the tools looked notable, and notability is correlated with having raised money in a particular window. What it does establish is the shape of the risk. These are not obscure projects, the window is short, and none of the six announced anything to the DAOs still depending on them. The disappearance was discovered by dig, not by an email.
Two treasury tools outside that sample, checked on 14 September 2026, show both ways a vendor can leave. Coinshift, a treasury-management app for crypto organisations built on Safe, said so in writing: its app host beta.coinshift.xyz still carries the notice “We are sunsetting Coinshift Business by 31st March 2026”, six months past that date (re-checked 2 October 2026).
The company had already moved twice: in 2025 to csUSDL, a yield vault over Paxos's USDL that stopped taking deposits after Paxos wound USDL down in October 2025, and by March 2026 to iUSPC, an “institutional credit yield” product that now fills the apex coinshift.xyz – out of the category, with the old app left standing behind the notice and the docs still describing both earlier products. Parcel, which sold “spend management for on-chain teams” to Safe owners, contributors and accountants, left no notice on its own domain: the Wayback Machine holds its marketing site in December 2024, a Vercel DEPLOYMENT_DISABLED response in May 2025 and a GoDaddy parking page by June 2026, and parcel.money now has no DNS A record.
The useful question is not how important a tool feels but what would be irretrievable if it vanished overnight. Three classes behave completely differently.
A dead interface is recoverable. When a tool is a view over state that lives on-chain, its death costs convenience and nothing else: the proposals, votes and balances are still there, and anyone can read the contract or build another front end. Tally's 2026 wind-down is the worked example, and the reason it was survivable is precisely that the Governor contracts it fronted never stopped working.
Aragon's own relaunch shows the same boundary inside one vendor. On 30 June 2025 the current Aragon app replaced every earlier version, and existing DAOs had nothing to do, because their proposals and settings live in OSx contracts. The developer layer fared differently: Aragon deprecated its legacy SDK and subgraph for OSx 1.3 and earlier and said it would not update either for version 1.4 or later, so an integration built on them cannot follow its DAO past 1.3 (Aragon).
A dead hosted record is lossy, and the loss is the reasoning. Workspaces, forums, and payment apps hold the material that never had an on-chain shadow: the draft that became a proposal, the objection that changed it, who held which role in which month, what an invoice was for. When CharmVerse's application host stopped resolving, that class of material went with it. A DAO in this position keeps its money and its contracts and loses its memory, which is the half that made the money legible. The same boundary shows up even in healthy tools: Den adds no contracts to Safe, so the human-readable description a signer reads sits on Den's servers next to a payload that is immutable on-chain.
A live contract with a dead maintainer is the dangerous one. Deployed contracts do not shut down. An unmaintained module that still holds a role on a treasury Safe, a badge contract that still gates membership, a streaming contract that still holds a balance: all of these keep executing exactly as deployed, which is the problem. Nobody ships the fix, nobody answers the disclosure email, and the standing permission outlives the company that asked for it. A dead front end is an inconvenience. A live privileged contract with nobody behind it is an open item on the attack surface.
Every check people reach for first is unreliable, and the failures are systematic rather than random.
charmverse.io and utopialabs.com answered 200 while the product behind them was gone. Domains outlive products because renewing a domain is cheap and shutting one down is a decision nobody gets around to making.utopialabs.com now serves 7,677 bytes of a live aircraft business on a domain that changed hands, so it reads healthy on status and size while the DAO payments product is as gone as it ever was. charmverse.io now answers 114 bytes – a window.onload hop to /lander – so it reads dead on size while the lander behind it is unchanged. A byte count tells you who is paying for the domain this month, not whether the product exists. The rarer failure is the one to watch for: a new occupant makes a dead tool look alive on every cheap signal at once, and the Internet Archive has no capture of the Atlas page to contradict it.docs.gelato.cloud, the documentation link on Gelato's own homepage, returns a Vercel DEPLOYMENT_NOT_FOUND at every path (checked 1, 9 and 20 September 2026, the last of them with the link still on the homepage). Nothing about the vendor is dead; its priceable terms are. Documentation is a hosted record with the same single point of failure as a workspace or a forum, and the archive is a poor substitute for a docs site that renders its tables after hydration – what that cost one figure is set out on who pays to execute a passed proposal.The check that actually works takes about a minute per tool and needs no API key: resolve the application host (dig +short app.example.com A), fetch it and read what came back rather than only how much of it there was (a byte count can grow because a different company bought the domain), and read pushed_at and archived from api.github.com/repos/<org>/<repo>. Run it against your own stack before you need the answer.
DAOs have built real process around money. A service provider is selected through a scored public process, funded by a proposal, and renewed by another one. Delegate payrolls and governance operating costs appear as budget lines that somebody argues about every season.
Tooling almost never gets there. It is adopted by a contributor with a company card, at a price too small to reach a proposal threshold, and it becomes load-bearing through use rather than through a decision. The result is an inversion: the dependencies with the most governance process attached are the ones the DAO could most easily replace, and the ones holding its actual working record have no proposal, no renewal date, no termination clause, and no named owner. When they fail, the failure surfaces as a support ticket that nobody can file.
This is also why discontinuity rarely appears in post-mortems. It produces no vote to point at and no on-chain event to timestamp, so it leaves the same kind of no-trace gap as the decisions that never became proposals.
HTTP 200 with the right content type indefinitely. Boardroom's front end errors on every data route while every link to it stays green. Liveness has to be checked by loading the thing and looking, or by calling the service it depends on; a status code cannot see it.The wider pattern is visible across the tooling this wiki already covers: Aragon dissolved its association and refocused on a product, Coordinape sunset its app, Superfluid deprecated a major interface, and Boardroom, having had to say out loud that it has no plan to deprecate, now errors on every data route of its public app while its API keeps answering (checked 22 August 2026). Polkassembly, Polkadot's main referendum front end for six years and paid by treasury referenda throughout, closed in 2026 after its wind-down request was rejected; the votes stayed on-chain and the discussion threads went into a read-only archive. Discontinuity is the normal condition of this layer, not an exception in it.
A caper keeps the record that hosted tools lose inside its own state on the Radix ledger. Its proposals, their options, the ballots cast and each proposal's title and description sit in the caper's own component, and anyone can read them back off the ledger without caper.network. No vendor database holds the reasoning beside the payload.
The record also sits apart from the rules. Each caper's state is deployed once and never migrated, while the rules that read and change it live in a separate part that can be upgraded, so replacing Caper's logic does not move the record. No third-party tool holds a standing role over the treasury, which removes the orphaned-contract failure this page describes rather than guarding against it.
This covers the record, not the interface. caper.network is a front end like any other. A reader who loses it can still get the proposals, the ballots and the outcomes off the ledger, which is the property that made Tally's wind-down survivable, applied to the part of the record most DAOs keep somewhere else.