Introduction
Tefily is a metadata-driven backend platform. You define collections, fields, HTTP endpoints, and access rules in the console. The server interprets that metadata on every request — you do not maintain generated server code.
Your apps talk to a per-project data API. Optional products in the same project cover hosting, git, analytics, project management, and a visual UI builder.
Tefily vs Kataflax
Section titled “Tefily vs Kataflax”Tefily is the public product name. In code and package names you will still see Kataflax: KataflaxClient, @kataflax/sdk, kataflax_client_sdk. Those are the same platform.
What you build against
Section titled “What you build against”| You use | For |
|---|---|
| Console | Orgs, projects, schemas, rules, hosting, git |
Data API /api/p/:projectId |
Auth, CRUD, files from your app |
@kataflax/sdk or kataflax_client_sdk |
Client apps |
Service tokens (kfxs_…) |
Your backend only |
Personal access tokens (kfx_…) |
MCP, scripts, admin SDK |
| MCP | Cursor and other AI clients |
Credentials
Section titled “Credentials”There are three credentials you will mix. Mixing them up is the most common source of 401s and “rules not applying”.
| Credential | Prefix / shape | Calls | Access rules |
|---|---|---|---|
| Platform JWT or PAT | JWT, or kfx_… |
Console APIs and the data API | Data API bypasses end-user rules |
| Service token | kfxs_… |
Data API only, plus POST .../auth/verify |
Bypasses end-user rules |
| Project user JWT | JWT with type: project |
Data API | Subject to access rules |
Never ship a service token (kfxs_…) or a personal access token (kfx_…) in a browser or mobile app. Use a project user JWT there.
- Quickstart — create a table and read it from JavaScript
- Concepts — org, project, collection, endpoint, rule
- Environments —
api.tefily.comvs local