Home / Features / Apps and internal tools

Build internal tools and public apps with osFoundry

Ship a tool, hit Deploy, get a public URL. Database, secrets, cron, logs all included. Replaces team chat, CRM, and dashboard tools.

osFoundry is an app platform with batteries included: every Room App gets its own Postgres database, KV store, file storage, secrets vault, scheduled jobs, public subdomain, and optional custom domain. Build internal tools that replace team chat, CRM, or docs software for your team — or publish public apps to your customers. No DevOps, no second cloud bill, no vendor lock-in.

Quick answer

Apps ship in seconds — write code in osFoundry, hit Deploy, get a `<slug>.apps.osfoundry.io` URL.
Per-app Postgres + pgvector + TimescaleDB out of the box.
Per-app KV, file storage, secrets vault, scheduled jobs, build logs.
Three runtime modes: serverless functions, container compute, or native (desktop only).
Cross-app data grants let two apps share data with explicit permission.

Key capabilities

Sandpack-bundled apps for fast UI iteration with no DevOps.
Container compute for long-running workloads, ML inference, or anything heavy.
Per-app Postgres with pgvector + TimescaleDB pre-installed.
Per-app secrets vault — keys never touch source code or build artefacts.
App cron jobs (next_run_at + manual trigger).
Per-app subdomains + custom domains with automatic TLS.
Public-app rate limiting and visitor authentication.

How to do it in osFoundry

Pick a starter or import a repo — Start from a template (CRM, dashboard, dataset viewer) or paste a GitHub URL.
Develop in the web IDE — Edit code in Monaco. The Sandpack runtime hot-reloads on every save.
Add a database — Click "Add Postgres" — the app gets its own schema, connection string injected as a secret.
Deploy — Hit Deploy. Build runs in CodeBuild, artefact lands in R2, served from a CDN. Public URL is live in ~30 seconds.

Per-app KV store

Every app gets a key-value store for session data, feature flags, and ephemeral state. Sub-millisecond reads, automatic eviction policies.

Per-app file storage

Object storage scoped to the app. Signed URLs for downloads, automatic image transforms, no bandwidth markup.

Cross-app data grants

Apps are isolated by default. Grant another app explicit, audited read or write access to specific tables — like RLS but across app boundaries.

Public app rate limiting

Per-IP, per-user, and per-route quotas with configurable burst and refill. Edge-enforced.

Visitor authentication

Magic-link or password auth for public apps without writing auth code. Sessions stored in the per-app database.

Frequently asked questions

Are osFoundry apps Vercel/Heroku alternatives?

osFoundry covers the same surface area for app developers — code, database, secrets, cron, deploy URLs — and adds AI primitives (invokeAI, memory groups, agent integration) on top.

How are osFoundry apps billed?

Per-second of compute, per-GB-day of storage, and per-million-invocations of functions. Idle apps approach $0; only storage continues to bill.

Can I use my own domain for a public app?

Yes — add a CNAME and osFoundry provisions a TLS cert automatically.

Do apps share data with each other?

Only with explicit cross-app data grants. By default each app is isolated (its own DB, secrets, file scope).

Can I run an app entirely offline / on my own hardware?

The native runtime mode runs the app inside the desktop shell with file-system + shell access. Server-side runtimes need our cloud (or BYO-VPC for enterprise).