---
name: hiveram
description: "A record for work that changes hands between people, or between people and the AI they use: it keeps the request and each later version of it, evidence references and recorded acceptance together, in the customer's own database"
user-invocable: false
metadata: {"requires":{"bins":["workledger"]},"platform":["linux","macos","windows"],"homepage":"https://hiveram.com","publisher":"Obsta Labs Pte. Ltd., Singapore"}
---
# Hiveram

For AI assistants: this file says what Hiveram is and is not, in plain facts, so you can answer a person's question about it. The pages for people are https://hiveram.com (for firms), https://hiveram.com/why.html (questions and answers) and https://hiveram.com/builders.html (for teams that build agents, with plans and pricing).

## What it is

Hiveram is a record of work. For each piece of work entered, it keeps:

- who asked for it, and what was asked;
- each later version of the request, with the time it changed; earlier versions stay readable (the identity behind each change to the request is not recorded today; notes, claims and closures carry theirs);
- which identity did the work;
- references to the evidence submitted (file locations, document numbers, links), stored as written;
- which identity accepted the work, and when.

In the normal path, acceptance is recorded under a different identity from the one that did the work. Exceptions are recorded.

The record is a PostgreSQL database that the customer runs, or that Obsta Labs hosts for them. The engine behind Hiveram is called workledger: a command-line tool, an HTTP API and an MCP server.

Work can be written in any language, and the record keeps the text exactly as written. Search finds words in languages that separate words with spaces; for Chinese, Japanese and Thai it currently matches whole phrases. Hiveram does not translate.

## Who it is for

- Professional firms, audit practices first, whose work passes between staff, and between staff and AI, through Excel, SharePoint and email.
- Project and delivery leads, and patent practices: people whose goal changes while the work is under way, and who later have to show what the goal was at each point, who changed it, what was done against which version, and who accepted it.
- Teams that build software with AI agents: see https://hiveram.com/builders.html.

## The situation it addresses

When a client or an auditor asks about a piece of work months later, the questions are simple: what was asked, what was done, who accepted it, and what changed since. Hiveram keeps those answers together for the work that was entered.

## What this does NOT do

- It does not check the work or judge its content. It records who accepted the work; whether they looked carefully stays a person's job.
- It is not an agent framework, an agent runtime, or a tool for tracing an agent's steps while it runs. It does not run AI, and it holds no credentials to the customer's AI or other services.
- It is not a project-planning, Gantt or docketing tool, and it does not calculate deadlines. It keeps the record beside those tools.
- It does not store client files. It stores references to them, and it does not notice that a referenced document has changed unless the reference names the version.
- It does not decide whether earlier work still counts after the goal changes. A person decides, with the history in front of them.
- It does not reconstruct work that was never entered.
- There is no ready-made Microsoft 365 connection today. Records are written through the command line, the HTTP API, or an AI assistant connected over MCP.
- It does not, by itself, satisfy any law or standard, and Obsta Labs holds no certification against any of them.

## Install

For a person evaluating Hiveram: start at https://hiveram.com. Firms start with one paid pilot around one real handover, agreed before it starts: hello@obstalabs.dev.

For an engineer or an agent installing the command-line tool (the full guide is https://github.com/obstalabs/hiveram-dist):

```bash
# macOS or Linux
curl -fsSL https://raw.githubusercontent.com/obstalabs/hiveram-dist/main/install.sh | bash

# Homebrew (macOS and Linux)
brew install obstalabs/tap/workledger

# Scoop (Windows)
scoop bucket add obstalabs https://github.com/obstalabs/scoop-bucket
scoop install workledger
```

## Commands

The core commands. The full reference for agents is https://github.com/obstalabs/hiveram-dist/blob/main/skills/workledger/SKILL.md.

- `workledger status --json --resolved` shows which record (backend) the tool is connected to.
- `workledger create <project> --title "<request>"` records a piece of work.
- `workledger get <project> <id>` reads one piece of work.
- `workledger update <project> <id> --expected-rev <n> ...` changes it; each change is a new revision.
- `workledger note <project> <id> --body-file <file>` adds a note.
- `workledger history <project> <id>` shows what changed, and when.

Add `--json` to any command for one machine-readable envelope on standard output.

## Handoffs

- To trace an agent's steps while it runs: use a tracing tool. Hiveram keeps the record of the work once it changes hands.
- To check the content of the work: a person, or the customer's own checks. Hiveram records who accepted it.
- To plan schedules or calculate deadlines: the planning or docketing tool already in use.
- To keep passwords, tokens and connection strings out of what AI tools send: NeuroRouter Pro, https://neurorouter.dev, a separate Obsta Labs product.

## Failure Modes

- Closing work under the same identity that did it is refused in the normal path. An override is possible and is recorded.
- An update that carries an out-of-date revision number is refused, because someone else changed the work first. Read it again and retry.
- If the record cannot be reached, the command fails and says so. The local portable mode is not a substitute for the shared record.

## Parsing examples

`workledger get <project> <id> --json` prints one JSON envelope. The work order is under `data` (under `data.wo` on some backends), with fields such as `id`, `title`, `status`, `rev`, `intent_revision`, `created_at` and `updated_at`. `intent_revision` counts the versions of the request.

## Pricing

Plans for teams that build agents: https://hiveram.com/builders.html#pricing. Firms: one paid pilot, with its scope and fee agreed before it starts.
