GoOmni
Download

GoOmni Spine

Share everything you build. Including how you built it.

GoOmni Spine keeps the finished work together with the data, the sources, and the steps behind it. So anyone, a teammate or an agent, can open it and keep building.

DocumentsDashboardsReportsProposalsAppsTools
Start with GoOmni DevRead the docs
ACME RFP response · history

Version history

Share linkRefresh from source
JLRefreshed pricing from knowledge basecurrent
now
v6 · 9a51…b4$0.42
AIAgent rewrote executive summary
2h ago
v5 · 7c02…e1$0.31
MKAdded compliance section
yesterday
v4 · 3d9f…aa$0.12

The problem

Today the work travels, but how you built it stays behind.

The finished file gets shared. The data, the sources, and the steps that made it do not. So the next person cannot really pick it up.

A designer builds a screen

↓ then

To hand it to a developer, they keep it simple enough to rebuild by hand. The small touches they wanted get dropped.

Someone builds a tool that works

↓ then

It lives in a developer tool the rest of the team does not use, so it never gets picked up again.

A team builds a dashboard

↓ then

The business team gets the finished dashboard, not how it was built. So they cannot change it or suggest edits.

Spine sends both. The work, and how it was made.

What is inside

Open format

The whole thing stays together, in one open file.

Every deliverable keeps the finished work, its data, its sources, and the exact steps and models that made it. Open it in our tool or read it without us. It is yours.

  • Content and data
  • Steps and models
  • Readable without our tool
deliverable.spine · open format

Inside every deliverable

Open source · MIT
content.mdthe finished work
structure.jsonhow it is organized
recipe.jsonthe steps and models used
sources/the data it was built on
media/images and assets

Readable without our tool. It is yours forever.

For the person you send it to

Living deliverable

Send a link, not a file. They can refresh it and tweak it.

The person on the other side opens a simple viewer. They press refresh to pull the latest numbers from the source, ask for a change in plain words, and download a clean copy. No tool to learn.

  • Refresh from source
  • Tweak in plain words
  • Download a clean copy
ACME RFP response · shared with your client

Executive summary

Refresh from sourceDownload
$4.2M · synced from knowledge base
Make the summary shorter and add the timelineTweak with AI

Open, and yours

An open format, driven by gni. Our open-source command line.

Think Git, but for everything your team builds after code. gni is a free command on npm that versions each deliverable with its data, sources, model, and cost, offline and with no account. The hosted service that governs it across a company is our business, like the company behind Git hosting.

zsh · gni
❯

npm i -g @goomni/cli, then gni anywhere. MIT licensed.

Open, yours forever

  • The gni command line, free on npm
  • The open bundle format each deliverable is saved in
  • The content-addressed store that keeps every version
  • The local engine that reads and writes it, offline

Hosted, our business

  • Governance and access control across your whole company
  • Cost visibility and budgets for every team
  • The cloud that runs it at scale, with support

Why it matters

Keep the work, and how you built it, together.

01

Everything comes with it

The files, data, and steps it was built from are kept right with the finished work.

02

Every version is clear

See what each version changed, not just the final one. Roll back any time.

03

Others build on it safely

Teammates or agents can prototype and suggest edits. You review before anything ships.

Hand off the whole thing, not just the final result.

The next person picks up right where you left off.

Start with GoOmni DevBook a demo