Sqitch

Rejected sequential migrations on principle.

What it is sold for

Managing schema changes across database engines.

Named alongside

These entries mention each other by name. It is a weak relationship and it is the only one the catalogue can show without inventing something.

Names:

• Plain
  Composable customer support infrastructure for B2B teams, assembled rather than configured.

Same shelf

The rest of data, apis and backends, alphabetically. Sharing a category is a filing decision, not a relationship.

• Agentset
  Open-source retrieval infrastructure for question answering, with the pipeline exposed rather than hidden behind an endpoint.
• Airtable
  A relational database wearing a spreadsheet, with automations and an API on top.
• Algolia
  Hosted search built for typing latency, with ranking and synonyms as configuration rather than as code.
• Apitable
  An open-source visual database with automation, positioned against the closed spreadsheet-database products.
• Appwrite
  An open-source backend server bundling auth, databases, storage and functions behind one API.
• Bytebase
  Schema migration and change review for databases, with the same approval flow across twenty engines.
• Cognee
  Open-source memory for agents, combining graph, vector and relational retrieval so recall survives the session.
• CrateDB
  A distributed SQL database for time series and real-time analytics at volumes a single node cannot hold.

All 35 in data, apis and backends