osFoundry / Platform
Per-app subdomains
Each app gets `<slug>.apps.osfoundry.io`. SSL automatic. Bring your own domain too.
What it is
Per-app subdomains give every app you build inside osFoundry a real, shareable web address of its own. When you publish an app, it comes up at `<slug>.apps.osfoundry.io` — the slug is the app's name, so the URL is predictable and human-readable instead of a random hosting string. There is nothing to configure on a DNS provider, no hosting account to wire up, and no certificate to request: the subdomain and its HTTPS certificate exist the moment the app is live.
Inside osFoundry, apps sit alongside your chat, agents, code, knowledge, and data in one BYOK workspace. Because osFoundry is local-first and you bring your own keys, the app you build talks to whichever models you've connected — local, cloud, or self-hosted — with no reseller layer in between. The subdomain is the front door that turns that app from something running in your workspace into something a teammate, a client, or the public can open in a browser. SSL is handled automatically, so every app is served over HTTPS from the first request; you never touch a certificate file or renewal.
When a project outgrows the shared `apps.osfoundry.io` namespace, you can bring your own domain and point it at the app instead, so it serves under your brand rather than the osFoundry subdomain. This matters because a memorable, branded, secure URL is the difference between a demo you screen-share and a product people bookmark — and getting there normally means standing up hosting, DNS, and TLS by hand. Per-app subdomains collapse that into publishing the app.
Key capabilities
- Every published app gets a predictable address at <slug>.apps.osfoundry.io, named after the app itself
- Automatic SSL means each app is served over HTTPS from the first request, with no certificate to request or renew
- Bring your own domain to serve an app under your own brand instead of the apps.osfoundry.io subdomain
- No DNS records, hosting account, or TLS setup to manage — the subdomain and certificate exist the moment the app is live
- Apps live in the same BYOK workspace as your chat, agents, code, and data, and run on the models you connect
Use cases
- Solo builder: ships an internal tool and shares one clean HTTPS link with the team instead of screen-sharing a local preview
- Consultant: maps a client's own domain onto an app so it looks and feels like the client's product, not a hosting subdomain
- Product team: spins up several apps in one workspace, each landing at its own readable subdomain for quick review and demos
Frequently asked questions
What URL does my app get when I publish it?
It gets `<slug>.apps.osfoundry.io`, where the slug comes from the app's name. The address is readable and predictable rather than a random hosting string, so it's easy to share and remember.
Do I have to set up an SSL certificate myself?
No. SSL is automatic. Each app is served over HTTPS from the moment it's live, and there's no certificate to request, install, or renew.
Can I use my own domain instead of the osFoundry subdomain?
Yes. You can bring your own domain and point it at the app so it serves under your brand instead of `apps.osfoundry.io`. The default subdomain remains available whether or not you add a custom one.