No. Tefily is metadata-driven at runtime. You change schemas, endpoints, and rules in the console. The API updates without a regenerate-and-redeploy loop for every model tweak.
You edit the schema in the console. The data API is already live.
Tefily reads collections, fields, and access rules from the console and serves
them at /api/p/:projectId. Hosting, git, DNS, project management,
dashboards, a UI builder, and agents share that project when you want them.
posts
collection
title
string
status
string
views
number
published
boolean
requireAuth · owner
GET /api/p/:projectId/posts
Database
Define the collection in the console. List, get, create, update, and delete are already on the project API, including file fields and an API tester.
- Field types: string, number, boolean, datetime, array, map, reference, file
- Access rules: requireAuth, field compare, role checks, file size and MIME limits
- Project auth on a
_userscollection, with JWTs for end users - Service tokens (
kfxs_…) for your own backends
The client packages are still @kataflax/sdk and kataflax_client_sdk.
Database details
import { KataflaxClient } from '@kataflax/sdk';
const client = new KataflaxClient({
baseUrl: 'https://api.tefily.com',
projectId: 'YOUR_PROJECT_ID',
});
await client.auth.login({
email: 'user@example.com',
password: 'password',
});
const page = await client.collection('posts')
.where('status', { isEqualTo: 'published' })
.orderBy('views', { descending: true })
.list({ page: 1, pageSize: 10 });final client = KataflaxClient(
baseUrl: 'https://api.tefily.com',
projectId: 'YOUR_PROJECT_ID',
);
await client.auth.login(
email: 'user@example.com',
password: 'password',
);
final posts = await client.collection('posts')
.where('status', isEqualTo: 'published')
.orderBy('views', descending: true)
.list(page: 1, pageSize: 10);Use one product, or all of them
Same project, same org, same bill. A project can be Database only.
- Hosting Containers and static sites. Buildpacks, logs, custom hostnames.
- Git Repos, diffs, merge requests, HTTPS and SSH.
- Project management Issues, cycles, modules, and intake inside the project.
- Dashboards Charts over Database collections on a 40-column canvas.
- UI builder Visual Flutter pages, bindings, and a device preview.
- DNS Zones and records, manual or Cloudflare.
- Agents In-project assistant, coding-agent runs, and MCP.
Free, Pro, Scale
Pro includes $10 of usage credit. Scale includes $60. Overage runs only if you turn on-demand on.
FAQ
No. A project can be Database-only. Hosting, Git, DNS, Project management, UI builder, and agents are there when you want them, behind the same org and permissions.
Hosting runs container backends via buildpacks (or an archive) and publishes static sites. Link a Git repo for auto-deploy on push, or upload a tarball. Custom domains go through DNS.
Open the console
Create an org, make a project, add a collection. Free plan. No card.