Features

The product surface for AI apps that need to leave the chat.

tertAI isn’t another model. It’s hosting, permissions, durable data, and an honest conversion layer - so prototypes become shareable tools.

Paste, GitHub, or zip

Drop HTML, a public repo, or a project zip. tertAI detects the shape and routes it to the right publish path.

Friendly app URLs

Name your app “Aakash” and get /a/aakash-app. If that name is taken, we reserve something like /a/aakash1931-app automatically.

Access modes

Anyone with the link, specific emails, or a company domain. Gates run before the app HTML is served.

Managed database

Forms auto-save. Apps can call tert.save / list / update / remove. Data survives redeploys.

Row-level policies

Declarative rules - hide until N submissions, unique fields, ownership - enforced server-side in the data API.

Publish reports

After conversion we show what we preserved, dropped, and what is no longer enforced. Explicit beats magic.

Secrets settings

We detect .env files, warn on live-key patterns, store values encrypted, and only inject public-safe keys.

Owner-only Responses

Visitors can submit forms. Only the app owner sees the Responses panel and Data table of what was filled in.

Express → static conversion

Common Express + public/ apps become a hosted UI wired to tertAI collections - without running their Node process.

Build repair

Platform build first; AI repair only when needed. Friendly messages for failures like native SQLite compile walls.

Isolation headers

Hosted apps run under a CSP sandbox without allow-same-origin so they don’t share the tertAI cookie jar.

Admin live panel

Platform admins see live visitors, every deploy link, and can delete apps or purge a user’s connected data.

Ready to publish?

Drop code, pick who sees it, get a live link.

Open dashboard