Can I use my own domain with sourcehut pages, and how does TLS work?

Yes. sourcehut pages gives every sourcehut user a username.srht.site domain, and it also supports bringing your own domain (BYOD). TLS is automatic and zero-config, so you don't manage certificates yourself whether you use the provided domain or your own.

Domains: what you get and what you can add

sourcehut pages is a tool for publishing static websites. The domain situation is straightforward:

The provided domain requires no setup beyond having a sourcehut account. If you want a custom domain instead of (or in addition to) the srht.site address, that's the BYOD path.

How TLS works

TLS on sourcehut pages is described as automatic, zero-config. In practice that means:

• You don't generate, upload, or renew certificates manually.
• The same automatic TLS applies whether you use the provided username.srht.site domain or your own domain.

Because TLS is handled for you, the main work on the BYOD path is the domain configuration itself, not certificate management.

What you can publish

sourcehut pages is for static websites, and it's generator-agnostic. The documentation names Jekyll, Hugo, and Doxygen as examples, and notes that any content generator works, including one you write yourself. So the domain and TLS setup doesn't depend on which generator you use.

Where to look for the actual steps

The sourcehut pages documentation is organized around the tasks you'll need:

• Quick start — get published quickly (the site claims you can be published in 3 minutes)
• Custom domains — the BYOD configuration
• Automating deployments — for repeatable publishing
• Managing Permissions — access control for your site
• Advanced settings
• Limitations
• REST API and GraphQL API
• Gemini support
• FAQ

For the exact custom-domain records and any per-domain settings, the Custom domains section is the authoritative entry point; the Quick start section covers the default username.srht.site flow.

Practical notes

• If you only need a site online fast, use the provided username.srht.site domain — no domain configuration needed, and TLS is already handled.
• If you need your own domain, plan for the BYOD configuration in the Custom domains docs; TLS remains automatic either way.
• The provided page material does not state pricing or login requirements for these features, so check the sourcehut pages site itself for current terms before relying on any assumption about cost or access.