TaglyDBTaglyDB
PricingDocsSign in
JSON & blobs, tagged

Tag it. Find it. Skip the schema.

TaglyDB is a JSON and blob storage API built around one idea: most of the data your scripts, pipelines, and workflows produce doesn't need a schema — it needs tags, and a place to put the result. That's it. Store a JSON payload or a blob, attach whatever tags actually describe it, and ask for it back later by exactly the combination that matters. If you've ever reached for Postgres or DynamoDB just to store something you'll only ever look up by two or three attributes, this is the thing you actually wanted.

Get started for freeapi.taglydb.com
api.taglydb.com

Create an index, store a tagged result

$ curl -X POST https://api.taglydb.com/indexes \
     -H "Authorization: Bearer $TAGLYDB_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{ "key": "support-tickets", "type": "json" }'

{ "id": "a1c9", "key": "support-tickets", "type": "json" }

$ curl -X POST https://api.taglydb.com/indexes/a1c9/items \
     -H "Authorization: Bearer $TAGLYDB_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "tags": { "team": "billing", "priority": "high" },
       "data": { "subject": "Refund request", "amount": 42.5 }
     }'

Ask for exactly the combination that matters

# every high-priority ticket on the billing team
# repeat a key to OR, mix keys to AND
$ curl "https://api.taglydb.com/indexes/a1c9/items/data?tag=team=billing&tag=priority=high" \
     -H "Authorization: Bearer $TAGLYDB_API_KEY"

{
  "items": [
    {
      "id": "e42f",
      "key": null,
      "tags": { "team": "billing", "priority": "high" },
      "data": { "subject": "Refund request", "amount": 42.5 }
    }
  ]
}

* Using truncated UUIDs for brevity/illustration purposes.

Tag any kind of run. Filter it any way you need.

The pattern that made tools like MLflow and Weights & Biases useful for training runs works just as well for everything else you'd otherwise track in a spreadsheet or a one-off table: tag it, filter and compare by any combination, and sort by timestamp to know which one's current.

Benchmark comparisons
Running a sweep across model configs and batch sizes? Tag each result and filter by any combination — every run for a given model, every run at a given batch size, or the exact intersection.
{ model: "llama-70b", batch_size: "32" }
Feature-flag rollouts
Tag each result with the experiment and variant it belongs to, then pull back just the treatment group — no experiments table to design.
{ experiment: "checkout-v2", variant: "treatment" }
Inventory snapshots
Snapshot stock levels per warehouse and category on whatever schedule you like, then compare across regions or catalog segments without a table designed for it in advance.
{ warehouse: "sea-2", category: "electronics" }
Release tracking
Every deploy is just a tagged item: service, region, version. Re-tag the same combination on the next rollout — sort by timestamp and the newest one is your current release.
{ service: "api", region: "us-east-1", version: "2026.9.14" }

The same model covers your batch jobs, too.

A nightly report, a scheduled export, an ETL job's output — tag it with whatever your pipeline already knows about itself (run id, source, destination) and query it back later without ever having designed a table for it. Your data doesn't stop being useful just because you didn't plan its shape in advance.

Keys when you want them, tags when you don't.

Every index and item can carry an optional key — use one when something needs a stable identity, skip it when tags already do that job. Need to hand a result to something unauthenticated — a dashboard, a teammate, a CDN? Mint a signed, time-limited URL server-side and share it; no embedded credentials, and it expires on its own. Every integration gets its own API key, revocable individually, without touching the others.

Pricing

Requests spend credits: 1 credit per 1,000 rows read or per MB written, at least 0.01 credits a request, and 50 credits per GB of storage a day. How credits work

Developer

Coming soon

$10 per 10,000 credits

  • Prepaid credits that never expire
  • No storage cap
  • Top up whenever you need

Enterprise

Coming soon

Custom for teams at scale

  • Volume pricing
  • Dedicated support
  • Custom terms

Get an API key and store your first tagged object in under a minute.

Get started for free