Skip to main content

Frequently asked questions

For people building apps​

Do I need to write sign-in code?​

No. The Edge signs people in before a request reaches your app. Read the person from tc.auth.user() in the browser, tc.auth.user(req) on the server, or the verified X-TC-User header. Don't add login pages, OAuth libraries or session cookies.

Which languages and frameworks can I deploy?​

Anything with a Dockerfile, plus automatic detection for Node (Express, Hono, Fastify, Koa, NestJS, Next.js), Vite front-ends, Python (FastAPI, Flask, Streamlit) and plain HTML. See Runtimes and detection.

Do I need git?​

No. Every deployment keeps its exact source bundle, so rollback works without git. Use your own git if you like.

How do I get a database?​

You already have one: every project gets its own Postgres database. Add tables in Database › Tables, or ship SQL files in db/migrations/. See Database.

My app needs Salesforce (or SharePoint, or the ERP). What do I do?​

Just call it through the SDK, for example tc.int.salesforce.get('/query', { q: '...' }). Optionally declare it in tc.json with a purpose. If the project isn't allowed yet, vastframe files an access request when you deploy, the app goes live anyway, and those calls start working the moment someone approves. See Integrations.

Why does a colleague see "You can't open Budget FY27.xlsx" in my dashboard?​

Microsoft 365 data is read as the signed-in person, so people only see files they can already open. That's deliberate. To show the numbers to everyone who can open your app, ask once with Show data to everyone with app access on the project's Integrations page; the request names how many viewers can't open the file today.

Where do I put secrets?​

In Settings › Environment variables with Secret on, or tc env set NAME=value --secret. Secrets are write-only and injected at container start. Never commit them. For vendor credentials, use integrations instead: apps never see vendor credentials.

Can I make an app public on the internet?​

No. Every app, preview and file sits behind company sign-in. The broadest setting is Everyone in the org.

Why was my project archived?​

Projects nobody opens for 60 days get a nudge, and are archived 30 days later. Open it or select Renew in Settings to keep it. An archived project keeps its data and can be restored. See Project settings.

For IT​

How do we stay in control?​

Every app has an owner, a place in the org chart, an expiry and a cost. Admins see everything in Admin, can archive or transfer any project, and can pull a kill switch per project or per person. Integrations go through a catalog with approvers and maximum scopes, and every call is audited. See Administration.

What happens when an app's owner leaves?​

When the directory marks them disabled or removes them, their projects move to their nearest enabled manager, who's asked to keep, transfer or archive each one.

Do we have to recreate users and groups?​

No. With Microsoft Entra ID, people, managers, departments and groups are synced from Microsoft Graph. With another identity provider, use SCIM directory sync through WorkOS, or manage people in Admin › People.

Can we limit who creates apps?​

Yes. The Builder role is everyone by default; an Org Admin can restrict it to specific people or groups in Admin › Roles.

What does it cost?​

vastframe doesn't publish prices in these docs. Ask your vastframe contact. Infrastructure cost per app is visible in Admin › Cost.

For security reviewers​

Where does our data live?​

Self-hosted: in your Azure subscription, entirely. vastframe cloud: in vastframe's installation, isolated per organization. See Data residency.

How are organizations isolated on vastframe cloud?​

By Postgres forced row-level security on every tenant table, a non-owner application role without BYPASSRLS, per-tenant resource names and per-tenant token audiences. See Multi-tenancy and isolation.

Can an app leak an API key?​

App code doesn't hold vendor credentials, database superuser credentials or storage keys. The Integration Gateway and the storage service hold them, check grants on every call, and audit it.

How do apps know who the user is, and can that be forged?​

The Edge strips any client-supplied X-TC-User header and sends a fresh ES256-signed token, valid for 5 minutes and bound to the app's audience. Apps verify it against published keys. See Access & security.

Is vastframe generally available?​

Not yet. It's in early access: the platform is built and tested end to end on the local stack, and the Azure implementation is in progress. See Platform status.

Was this page helpful?