Tess vs Directus
Data platform over SQL databases (Node.js)
A Node.js platform that turns an existing SQL database into REST and GraphQL APIs with an admin app.
Side by side
| Criterion | Tess | Directus |
|---|---|---|
| Approach | Tess owns its storage and schema | Mirrors the tables of an existing SQL database |
| Databases | PostgreSQL, MySQL, SQLite, MongoDB, DynamoDB, RocksDB | SQL databases: PostgreSQL, MySQL, MariaDB, SQLite, MS SQL, Oracle, CockroachDB |
| API | GraphQL generated from the models | REST and GraphQL |
| Review workflow | Built in, per content type | Built with permissions and Flows |
| Automation | Plugins on every write | Flows (event-driven automation) built in |
| License | Community (personal use) / Enterprise (commercial use) | Business Source License: free under a revenue threshold, commercial license above |
Choose Directus if…
- You must expose an existing SQL database as is.
- You want built-in automation flows.
Choose Tess if…
- You start from content models, not from existing tables.
- You need NoSQL (MongoDB, DynamoDB) or an embedded database, or AWS Lambda.
Moving from Directus to Tess
Each Directus collection becomes a Tess content type, and its relational fields become RELATION fields. Write them in the tess-transfer YAML format, import them, then copy the items through both GraphQL APIs.
Facts checked on October 20, 2026 from Directus's public documentation (directus.io). Products change quickly: check the vendor's site for the latest features and pricing.