Skip to main content
Convex is a backend platform that replaces your database, server, and real-time layer with a single proprietary runtime. You write mutations, queries, and actions in Convex’s format, and your data lives in Convex’s document-oriented store. Specific takes a different approach: your coding agent defines standard infrastructure in a config file, and your code stays portable by building on open-source technology like PostgreSQL.
ConvexSpecific
Data modelProprietary document storeStandard PostgreSQL
Query languageConvex query/mutation functionsStandard SQL through Postgres
Backend logicConvex actions (JS/TS only)Any stack, standard backend code without lock-in
Real-timeReactive queries through SDKBuilt-in sync engine that works with any stack
Code portabilityTightly coupled to Convex runtimeStandard code with no vendor lock-in
StorageConvex file storage APIS3-compatible, any S3 client
Open-source foundationProprietary data store and runtimeStandard protocols like PostgreSQL and S3
Agent integrationNot designed for agentsAgent-first

Designed for coding agents

Convex targets human developers writing backend logic in its proprietary format — mutations, queries, and actions that follow Convex-specific conventions. This is a workflow optimized for humans reading Convex documentation. Specific is built so that coding agents define infrastructure, deploy services, and debug issues through a config file and CLI. This is the workflow agents are best at: writing configuration, running commands, and interpreting structured output.

Built on open-source, not proprietary infrastructure

Convex uses a proprietary document store and runtime that is not open-source. Your data lives in a system controlled by a single vendor, with no standard tooling ecosystem around it. Specific builds on battle-tested open-source technology: standard PostgreSQL for your data, S3-compatible storage, and Redis for caching. These are systems with decades of community support, tooling, and portability. If you ever need to move, your data and your knowledge transfer with you.

No vendor-specific code in your application

With Convex, your backend logic is written as Convex mutations, queries, and actions — a format that only runs on the Convex runtime. Your application code is tightly coupled to one platform. With Specific, you write a normal code using any programming language and stack, whatever fits your project. Your code is standard and portable. If you switch infrastructure providers, your application code still works.

Any language, not just TypeScript

Convex backend functions must be written in JavaScript or TypeScript. If your project needs a different language Convex can’t accommodate that. Specific supports any language or framework. Your services can run Node.js, Python, Go, Rust, or anything else. Pick the right tool for the job.