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, versioned API.
Governed accounts, workspaces, collections, immutable releases, API keys and REST delivery are implemented for the pilot and reachable by authorized pilot operators only. The MCP interface is deferred. Billing and public registration do not exist, and every page labels its own status.
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, requiring a tracked API key. An agent interface over the same releases is deferred until it can be built and verified.
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. They are synthetic illustration, not Bobby DB product data: no collection, entry or customer content has been created in production.
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 authorized operators 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 delivery
Clients read the current or a pinned release.
Built for machines first
Bobby DB exposes a versioned REST surface for applications, built around tracked API keys, release pinning and honest error reporting, and answering for authorized pilot operators only. An agent interface over the same releases is deferred.
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 key and invented collection slug. The credential shown is unmistakably fake.
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 makes a build reproducible.
Authorized pilot operators only
The versioned REST delivery surface is implemented and requires a tracked API key. It answers for authorized pilot operators only, and it has not been released beyond the pilot.
The MCP interface is deferred. Its address answers one stated refusal, exposes no data and holds no credential. It will be built only under separate authorization and verification.
The examples above 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 built with its decisions written down. The table below is the single canonical status catalogue this whole site reads from, so no two pages can disagree about what exists.
| Capability | Status | Who can use it | What is true today |
|---|---|---|---|
| Public marketing website | IMPLEMENTED — PILOT | Anyone | The public website, brand system and documentation index are implemented and served over HTTPS. |
| Email and password authentication | IMPLEMENTED — PILOT | Authorized pilot operators | Email and password is the only Bobby DB sign-in method, and it is implemented for the pilot. Authenticating creates no Bobby DB account, role, workspace access or authority: access is granted by the operator. |
| Public signup and self-registration | NOT YET AVAILABLE | Nobody | Registration is switched off in every environment and enforced on the server. There is no way to register yourself. |
| Operator-granted application access | AVAILABLE TO AUTHORIZED PILOT OPERATORS | Authorized pilot operators | Application access is granted by the Bobby DB operator to named pilot operators only. Signing in is not the same as being admitted. |
| Governed accounts and roles | IMPLEMENTED — PILOT | Authorized pilot operators | Accounts, platform roles and capability checks are implemented for the pilot, with an append-only audit trail. One governed pilot account exists, held by the Product Owner. |
| Workspaces | AVAILABLE TO AUTHORIZED PILOT OPERATORS | Authorized pilot operators | Workspaces are implemented as the isolation boundary and are reachable only by authorized pilot operators. No workspace has been created in production. |
| Collections and entries | AVAILABLE TO AUTHORIZED PILOT OPERATORS | Authorized pilot operators | Collections, schemas, groups and typed entries are implemented in the governed console for authorized pilot operators. No collection or entry has been created in production. |
| Immutable releases | AVAILABLE TO AUTHORIZED PILOT OPERATORS | Authorized pilot operators | Reviewed drafts become immutable, pinnable release versions. The lifecycle is implemented for authorized pilot operators, and no release has been published. |
| API keys | AVAILABLE TO AUTHORIZED PILOT OPERATORS | Authorized pilot operators | API keys are implemented: hashed at rest, shown once at creation, scoped to one workspace and revocable. Keys are issued to authorized pilot operators only, and none exists in production. |
| REST delivery | AVAILABLE TO AUTHORIZED PILOT OPERATORS | Authorized pilot operators | The versioned REST delivery surface is implemented and requires a tracked API key. It answers for authorized pilot operators only, and it has not been released beyond the pilot. |
| MCP interface | NOT YET AVAILABLE | Nobody | The MCP interface is deferred. Its address answers one stated refusal, exposes no data and holds no credential. It will be built only under separate authorization and verification. |
| Billing and paid plans | NOT YET AVAILABLE | Nobody | There is no checkout, no payment provider and no paid plan. The published plans are a pricing proposal only. |
| Google sign-in | NOT YET AVAILABLE | Bobby DB operator | Google is not offered as a Bobby DB sign-in method and appears nowhere in the product. It remains configured beneath the product purely as temporary operator lockout protection. |
| Bobby ID | NOT YET AVAILABLE | Nobody | Bobby ID is deferred. No Bobby ID sign-in exists and none is offered. |
| Bobby DB public Master Data | NOT YET AVAILABLE | Nobody | The Bobby DB-owned Master Data workspace is reserved and empty. Its content is supplied by the Product Owner, so no public collection is published and no counts, versions, sources or licences are claimed. |
Private by default
Implemented — pilotCollections are private unless a workspace deliberately publishes them, with authorization decided server-side against stored role assignments.
Keys are hashed
Implemented — pilotAPI keys are 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 in a governed pilot. There is no public registration and no billing: access is granted by the operator to named pilot operators. The product design, developer contracts and pricing proposal are published here so they can be judged.