Prototyping & Hackathons

One API call gets you a connection string. When you abandon the project (we all do), the database archives itself.

terminal

$ curl -X POST https://api.cinchdb.dev/v1/databases \

-H "Authorization: Bearer cinch_abc123..." \

-d '{"name": "hackathon-demo", "store_type": "cache"}'

{

"id": "db_7f3a...",

"host": "tcp.cinchdb.dev",

"port": 6379,

"status": "active"

}

$ redis-cli -h tcp.cinchdb.dev -p 6379 -a cinch_abc123...

tcp.cinchdb.dev:6379> SET hello world

No ops required

It's a hackathon. You don't want to configure instance sizes, pick regions, set up VPCs, or wait for provisioning wizards. You want a database.

→ One API call, milliseconds to ready.
→ Standard protocols — use whatever client library you already know
→ Auto-stops when idle. Abandoned projects don't generate bills.
→ Your prototype connection string works when you go to production. No migration step.

CACHE

Redis-compatible. Session storage, rate limiting, real-time features.

GRAPH

Cypher queries. Knowledge graphs, social networks, recommendations.

SQL

SQLite-compatible. Application data, user tables, structured storage.

Skip the provisioning and instance sizing. Just start building.