Small tools,
slightly unhingged.

unhingged is a small network of software that does one job each. Six tools so far, one sign-in between the apps, and a seventh on the bench.

Come in ↓
gg

About

unhingged is a home for small, sharp tools. Each one does a single job, keeps its own address and the apps share one sign-in. Nothing here is a suite.

About the spelling: yes, two g’s. One of them holds the word together. The other came loose, and we left it that way — it is a fair picture of how the tools get made. Flick it if you like.

Tools6

Vizu1/6

Comments that stick
to the element.

Drop one script into any page. Reviewers click an element and leave a note, and the note anchors to the element itself — not a screenshot, not a coordinate — so it is still there after the next deploy.

Open Vizu
  • One script tag, or a React provider
  • Anchors re-find their element after a refactor
  • An MCP endpoint, so your agent can read the comments

Terms2/6

Every version,
and who agreed to it.

Publish your Terms and Privacy Policy as immutable versions. One API call at sign-in tells you whether this user is on the latest, or has to accept before going any further.

Open Terms
  • Versions are files, and published ones never change
  • One question per sign-in: is this user up to date?
  • An acceptance log you can hand to an auditor

Timeit3/6

The hour
everyone’s free.

Pick some days and share one link. Everyone paints when they can make it, and the overlap shows you when to meet — in each person’s own time zone.

Open Timeit
  • Time zones worked out per viewer
  • Guests answer with just a name, if you allow it
  • The final time lands as a calendar file

Mockit4/6

Upload the spec,
every endpoint answers.

Give it an OpenAPI or Swagger document and get a base URL. Every path in the spec is live, answering with data that fits its schema — the right types, enums and formats, names that read like names. Seed it to make it repeatable, steer the status per call, pin an endpoint to a fixed answer, and read the request log.

Open Mockit
  • Examples written in the spec come back verbatim; the rest is generated
  • Status, seed and delay per call, in a header or the query string
  • An MCP endpoint, so your agent can upload a spec and call the mock

Reportit5/6

They ask and vote.
You ship, and tell them.

Open a workspace and your product has a page where people ask for things and vote on what matters. Triage what comes in, show what is planned on a public roadmap, and when it ships, write the changelog — everyone who voted for it gets an email. Your own app posts over an API key; your agent triages over MCP.

Open Reportit
  • One vote per account; the submit form looks for duplicates as you type
  • Every status change is written into the thread, with the team’s note
  • Publishing a changelog entry marks its posts complete and emails their voters

Logit6/6

A message template in,
a structured event out.

The library Serilog is for .NET, for JavaScript. Write a message template, with holes for the values, and every sink gets the same structured event: the console, a rolling file or an HTTP endpoint, as text, JSON or CLEF. It is a package you install, not a service — nothing passes through us.

Open Logit
  • Zero runtime dependencies, and one import that runs in Node, Bun, the browser and the edge
  • Console, rolling-file and HTTP sinks, writing text, JSON or CLEF
  • Serilog’s API and property names, so its docs and Seq dashboards carry over

Number seven
is on the bench.

It will turn up here when it works, at an address shaped like the others. No waitlist, no countdown.

Six tools.
One loose g.