Data, APIs and backends

Used here, in this category

• Cloudflare D1serves
  Holds the rate-limit and token state behind the CV gate. Nothing else on the site touches a database.
  Evidence: functions/_lib/gate.ts

All 35

Alphabetical. Checked on 2026-09-04; anything that did not answer says so.

• Agentset
  Open-source retrieval infrastructure for question answering, with the pipeline exposed rather than hidden behind an endpoint.
  RAG with the seams visible.
• Airtable
  A relational database wearing a spreadsheet, with automations and an API on top.
  The spreadsheet that admits it is a database.
• Algolia
  Hosted search built for typing latency, with ranking and synonyms as configuration rather than as code.
  Optimised for the keystroke, not the query.
• Apitable
  An open-source visual database with automation, positioned against the closed spreadsheet-database products.
  The Airtable shape, self-hostable.
• Appwrite
  An open-source backend server bundling auth, databases, storage and functions behind one API.
  The Firebase shape, self-hostable.
• Bytebase
  Schema migration and change review for databases, with the same approval flow across twenty engines.
  Code review, applied to the schema.
• Cognee
  Open-source memory for agents, combining graph, vector and relational retrieval so recall survives the session.
  Memory as infrastructure, not as a longer prompt.
• CrateDB
  A distributed SQL database for time series and real-time analytics at volumes a single node cannot hold.
  SQL on top of a shape that usually forces you off SQL.
• dbForge AI Assistant
  Writes, explains and optimises SQL inside a database IDE rather than in a chat window.
  Model help where the query plan is.
• DBT
  Transformation as version-controlled SQL with tests and lineage. Turned analytics work into software engineering.
  Brought code review to the warehouse.
• Directus
  Wraps an existing SQL database with an admin interface and REST, GraphQL and MCP APIs, without owning the schema.
  Points at your database instead of replacing it.
• Encore
  Infers infrastructure from application code, so the cloud resources come from what the program declares it needs.
  The application describes its own infrastructure.
• Firebase
  Google's mobile and web backend: realtime data, auth, hosting and functions with client SDKs.
  Made backendless development a real option.
• Flyway
  Versioned database migrations. Plain SQL files with an order and a checksum, which is most of the problem solved.
  Migration as a numbered file, and that is enough.
• Hasura
  Generates a GraphQL API over existing databases, so the API is a projection of the schema rather than hand-written.
  The API is derived, not maintained.
• Hive Intelligence
  Connects an agent to live cryptocurrency market data, with the source of each answer attached.
  Shows its working, which most data APIs do not.
• Jamsocket
  A backend for session-based applications and sync engines. Joining Modal.
  Absorbed: the team is moving to Modal.
• Liquibase
  Database change management with migrations expressed in XML, YAML, JSON or SQL, and rollback defined alongside.
  The one that always insisted on the rollback.
• Meilisearch
  An open-source search engine tuned for typo tolerance and instant results, simple enough to run yourself.
  Fast search without an Elasticsearch cluster.
• Neon
  Serverless Postgres with branching, so a database copy for a pull request costs almost nothing.
  Made branching a database a normal thing to do.
• Neuledge
  Prepackaged local documentation for coding assistants, so framework reference is available without rate limits.
  Docs cached locally, because the network is not free.
• Nhost
  Managed Postgres, GraphQL, auth, storage and functions as one backend, open-source underneath.
  The Supabase shape, through a GraphQL door.
• Outerbase
  A database interface with model assistance, aimed at people who need the data without knowing the schema.
  A database client for the rest of the team.
• PlanetScale
  Managed Vitess and Postgres with schema branching and non-blocking migrations at scale.
  Brought Vitess to teams who could never have run it.
• PocketBase
  An entire backend in a single Go binary: database, auth, file storage and admin interface.
  One file, which is the whole argument.
• Postman
  The API client that became the industry's shared workspace for specifications, mocks and tests.
  How most teams first learned to talk about an API.
• Retool AI
  Internal tools built from components over your own data, now with model features in the builder.
  The admin panel nobody wants to write, generated.
• Sqitch
  Database change management without a migration numbering scheme, using dependencies and plain SQL instead.
  Rejected sequential migrations on principle.
• Strapi
  An open-source headless CMS in JavaScript, self-hosted, with the content model defined in code.
  The CMS you run yourself.
• Supabase
  Postgres with auth, storage, realtime and generated APIs around it. The database is the product, not an abstraction over one.
  It is just Postgres, which is the whole argument.
• Supabase AI the page returns 404
  Supabase's AI features, listed separately. That page returns 404 and the capability lives inside the main product.
  Folded into the main product.
• Swiftype
  Hosted site and application search. Acquired by Elastic and folded into its search products.
  Absorbed into Elastic.
• Typesense Cloud
  Hosted typo-tolerant search on the open-source Typesense engine, distributed globally.
  Open engine, managed operation.
• Upstash
  Serverless Redis, vector and search, priced per request, which suits functions that idle most of the time.
  Pays nothing when nothing is happening.
• Websolr
  Hosted Apache Solr, a long-running option for teams already committed to Solr.
  Solr, without running Solr.

Other shelves