osFoundry / Platform
Custom domains
Attach your domains. CNAMEs verified, SSL auto-issued, downtime tracked.
What it is
Custom domains let you serve the apps, pages, and workspaces you build in osFoundry from your own domain name instead of a default platform URL. You point a CNAME record at osFoundry, the platform verifies the record, and once it resolves an SSL certificate is issued automatically so the domain loads over HTTPS. Downtime is tracked, so if your domain stops resolving or the certificate has a problem, you can see it rather than finding out from a visitor.
Inside osFoundry the flow is deliberately narrow. You enter the domain you want to attach, add the CNAME record it gives you at your DNS provider, and the platform polls until that record is verified. Verification is what gates certificate issuance: the SSL cert is only requested once the CNAME actually points where it should, which is why you occasionally wait on DNS propagation before the lock icon appears. After that, renewal and re-issuance are handled for you, and the domain's reachability is monitored so a broken record or an expired-then-renewed certificate surfaces as tracked downtime instead of silent failure.
This matters because osFoundry is a bring-your-own-key desktop workspace where you also build and publish things worth putting a real name on. A custom domain is what turns an internal app or a shared page into something that lives at your brand, not a generic subdomain. Because osFoundry is BYOK with no reseller markup on the AI you run, the domain feature follows the same principle: it is plumbing that connects your infrastructure to your work, not a place to be upsold. You own the domain, you control the DNS, and osFoundry verifies and secures it.
Key capabilities
- Attach one or more of your own domains to apps and pages built in osFoundry
- CNAME verification gates the process so SSL only issues once DNS actually resolves
- SSL certificates are issued and renewed automatically for HTTPS out of the box
- Downtime is tracked, so a broken CNAME or certificate problem surfaces instead of failing silently
- You keep control of your domain and DNS records; osFoundry verifies and secures, no reseller markup
Use cases
- Founder: publish a shared app at app.yourcompany.com instead of a default osFoundry subdomain, with HTTPS issued automatically
- Agency: attach a separate client domain to each delivered app and rely on tracked downtime to catch DNS or certificate issues early
- Developer: verify a CNAME once, let SSL renew on its own, and stop hand-managing certificates for internal tools
Frequently asked questions
How do I connect my domain to osFoundry?
Enter the domain you want to attach, add the CNAME record osFoundry gives you at your DNS provider, and wait for verification. Once the CNAME resolves, the SSL certificate is issued automatically and the domain serves over HTTPS. If it does not verify right away, it is usually DNS propagation, which can take some time to reach osFoundry's resolvers.
Do I have to buy or manage SSL certificates myself?
No. Once your CNAME is verified, SSL is auto-issued and renewed for you, so the domain loads over HTTPS without you requesting or rotating certificates. You keep ownership of the domain and its DNS; osFoundry handles verification and the certificate.
What happens if my domain goes down?
osFoundry tracks downtime for attached domains, so a CNAME that stops resolving or a certificate problem shows up as tracked downtime rather than a silent failure you only hear about from a visitor. That gives you a place to look when a domain is not loading.