OneCamp adds tables, a public API, and AI usage budgets

OneCamp is a self-hosted workspace that combines chat, documents, tasks, video calls, and AI tools. It is designed to run from a single file. The main change is that tables are not just placed inside documents as visual blocks.

They are separate workspace objects that people can view like , while AI tools and outside programs can query and use the same data. Each row stores a jsonb object keyed by field UUID instead of by the visible field name. That means a column can be renamed without rewriting stored data, and a new field can be added without changing every old row.

A public REST API, scoped personal tokens, an MCP server and client, and a TypeScript SDK were also added. Tokens are SHA-256 hashed, shown only once, and can have per-token rate limits. AI were also part of the sprint, but the working details are not specified.

Key points

  • OneCamp combines chat, docs, tasks, video calls, and AI in a self-hosted workspace.
  • Tables are treated as real workspace data, not just visual blocks inside documents.
  • The jsonb and field UUID design reduces work when columns are renamed or added.
  • The sprint added a public REST API, MCP server, TypeScript SDK, and scoped tokens.
  • Tokens are SHA-256 hashed, shown once, and can have rate limits per token.
Read original