Governed key-value data, ready for every product.
Store, organize and publish stable collections. Bobby DB is designed so you can use public master data with a tracked API key, or manage private collections through a simple API and MCP.
Accounts, API keys, collections and paid plans do not exist yet. This site documents the approved design and labels every capability that is still to be built.
Three things Bobby DB is designed to guarantee
Design commitments, stated as design rather than as operating behaviour.
Keys stay stable
Product previewA key is the contract. Values are typed and JSON-compatible, so a product can read the same key for years while the value behind it evolves through reviewed releases.
Releases are immutable
Product previewA reviewed draft becomes a version that never changes. Clients either follow the current release or pin an exact version, so a data change never silently alters a build.
Delivery is API-first
Product previewBobby DB is designed to be consumed by machines: a versioned REST surface for applications and an MCP endpoint for AI agents, both requiring a tracked API key.
A key-value model that a product can rely on
Entries are keys with typed, JSON-compatible values. Groups organise related keys inside a collection so a large reference set stays navigable.
Key / value shape
Illustrative| Key | Value | Type |
|---|---|---|
| example.plan.label | "Builder" | string |
| example.plan.request_cap | 1000000 | number |
| example.plan.addons_allowed | true | boolean |
| example.plan.limits | { "workspaces": 1, "members": 3 } | object |
| example.plan.tags | ["preview", "synthetic"] | array |
| example.plan.retired_at | null | null |
- Entry
- One key and one typed value, addressable on its own.
- Group
- A named set of related keys inside a collection.
- Collection
- The unit that is drafted, reviewed, released and served, public or private.
- Workspace
- The tenant boundary that owns collections, members and API keys.
Product preview
The values above are invented to show the shape of the model. No entry, collection or customer data exists in Bobby DB yet.
Public master data, published like software
Bobby DB will maintain a public master-data catalogue in a Bobby DB-owned workspace, released through the same reviewed workflow customers use for their own collections.
The Bobby DB public catalogue is empty. Nothing here is seeded, sampled or scraped: the Product Owner uploads the real Master Data into the Bobby DB-owned “Master Data” workspace through the governed draft, review and release workflow, and collections appear here only once a genuine immutable release exists.
Reading public collections will still require a valid API key, so usage can be metered and abuse stopped. Public availability is not the same as authority: every release is designed to carry its own provenance, licence and changelog so you can judge it yourself.
See the planned cataloguePlanned groups (14)
- Languages
- Countries
- Currencies
- Time Zones
- Country Subdivisions
- Country Calling Codes
- Continents and World Regions
- Measurement Units
- Locales and Formatting Profiles
- MIME and Media Types
- Colours and Standardized Colour Codes
- Public Holidays
- Address Formats
- Industry Classifications
Planned structure only. No collection is published, and no counts, versions, source dates or licences are claimed.
Draft, validate, review, release, deliver
One lifecycle for public master data and private customer collections alike.
STEP 1
Draft
Entries are edited freely inside a workspace collection.
STEP 2
Validate
The draft is checked against the collection's JSON Schema mode.
STEP 3
Review
A workspace member reviews the diff before anything is published.
STEP 4
Immutable release
An approved draft becomes a version that never changes.
STEP 5
REST / MCP delivery
Clients read the current or a pinned release.
Built for machines first
Bobby DB will expose a versioned REST surface for applications and an MCP endpoint for AI agents. Both are designed around API keys, release pinning and honest error reporting.
curl "https://bobbydb.com/api/v1/collections/example-collection/entries?limit=50" \
-H "Authorization: Bearer bdb_public_example_replace_me" \
-H "If-None-Match: \"example-etag\""Placeholder host, placeholder key, invented collection slug. Not a working endpoint.
curl "https://bobbydb.com/api/v1/collections/example-collection/entries?release=example-release-version" \
-H "Authorization: Bearer bdb_public_example_replace_me"Pinning a release is designed to make a build reproducible.
Not yet available
No REST endpoint and no MCP endpoint are deployed. The examples above document the planned contract, use unmistakably fake credentials, and never place a key in a URL.
Where AI stops
Bobby DB is designed to let AI propose changes, never to let AI publish them.
AI may propose
Planned- Draft a schema from an example payload.
- Suggest a mapping for an import.
- Explain a diff between two drafts in plain language.
AI may not decide
Planned- Approve a review or cut a release.
- Write directly into a released collection.
- Change access, keys, plans or governance.
A proposal is designed to arrive as a draft that a human reviews. Proposal work is metered in Bobby Credits, separately from ordinary request allowances. No AI provider is connected to Bobby DB today.
Plans and limits, proposed openly
Proposed pre-launch pricing. Plans cannot be purchased, no checkout exists, and final allowances depend on infrastructure and load-cost evidence that does not exist yet.
€0
Free
- 250,000 requests/month
- 1 workspace
- 1 team member
- 3 private collections
- 100 MB storage
€5/month or €50/year
Builder
- 1,000,000 requests/month
- 1 workspace
- 3 team members
- 25 private collections
- 1 GB storage
€15/month or €150/year
Pro
- 5,000,000 requests/month
- 3 workspaces
- 10 team members
- 100 private collections
- 5 GB storage
€39/month or €390/year
Business
- 20,000,000 requests/month
- 10 workspaces
- 50 team members
- 500 private collections
- 25 GB storage
No plan can be purchased and there is no checkout. Every plan has finite workspace and member allowances.
Governance you can inspect
Bobby DB is being built with its decisions written down. What exists today is a brand system and this public presentation; the platform's controls are design, not evidence.
Private by default
PlannedCollections are designed to be private unless a workspace deliberately publishes them, with authorization decided server-side.
Keys are hashed
PlannedAPI keys are designed to be stored as hashes and shown once at creation, with metadata retained for metering and revocation.
No claims we cannot prove
ImplementedNo certification, penetration test, uptime figure, SLA or customer claim appears anywhere on this site, because none can be evidenced.
Follow the build in the open
Bobby DB is not accepting sign-ups: authentication, workspaces and billing are not implemented. The product design, developer contracts and pricing proposal are all published here so they can be judged before anything ships.