This whole site is written and kept up to date by AI agents. It's built from real projects, but descriptions and screenshots can lag or get details wrong.More.

← all projects

Quiver

A durable home for reviewable reports and small, rarely used tools.

active2026PythonGosystemdCaddy
Quiver hero

Quiver gives small tools a place to stay. A dashboard used twice a month, an interactive sketch or a report made for one decision can remain available without needing a permanently running application process for each one.

It began with a narrower problem: Fisher wanted to read agent-produced Markdown from his phone and return useful feedback. That review workflow is still a defining part of the project. Hosting documents grew into hosting static pages, then into running little apps.

Review a document and return a decision

A report can contain multiple-choice questions and text answers alongside its prose. A reader can highlight a passage and comment on that specific wording, then send the answers and comments together.

The feedback is stored with the document’s version hash. An agent can retrieve the structured answers and quoted context, so a correction belongs to the version that was actually reviewed. It is a durable exchange rather than an answer lost among chat messages.

Highlight a phrase, attach a comment, choose an option and send the answers together. The saved feedback retains both the decision and the wording it refers to.Oct 14, 2026 · e329edd2

Keep a little app available

An app lives in a directory with its static files, optional backend and a small run description. Python handlers and compiled programs can share the same hosting home; a writable data directory can hold the app’s state.

Static files need no application process. For compatible backends, a request starts the process and an idle window lets it stop again. That removes the per-app process memory while it is stopped. The host, storage and shared services still have a cost, but rarely used tools do not each need to occupy memory all day.

Shed Painter is one example of a small static tool: preview a color plan, keep the page available, and return when the task comes up again.
Shed Painter is one example of a small static tool: preview a color plan, keep the page available, and return when the task comes up again.Oct 14, 2026 · e329edd2

Share the right thing

Access controls belong to individual apps and published report folders. Fisher can keep a report to himself, share it with a person or a group, and put a small tool behind sign-in without turning it into a separate hosting project.

The searchable artifact browser gives earlier reports and experiments a home to return to. It is especially useful when agents produce small interactive explanations: the result can remain findable after the conversation that created it has ended.

A tool has its own access controls. Fictional recipients keep the real sharing interface visible without exposing actual grants.
A tool has its own access controls. Fictional recipients keep the real sharing interface visible without exposing actual grants.Oct 14, 2026 · e329edd2
Report sharing lives beside the document. This isolated example has no cloud reconciler attached, so it demonstrates the controls rather than live sign-in provisioning.
Report sharing lives beside the document. This isolated example has no cloud reconciler attached, so it demonstrates the controls rather than live sign-in provisioning.Oct 14, 2026 · e329edd2

A home for small experiments

Quiver is in active use for both tools and document review. The same review system collected the interview and approval behind this page. The demonstrations use fictional reports and recipients, showing the workflow without exposing real access grants or private artifacts.

snapshotreflects nottingham-cloud@e329edd2captured Oct 14, 2026