Product

Domains

To use your own domain on Stackap you attach the hostname to a project, create the one DNS record Stackap shows you, and the HTTPS certificate switches on by itself once DNS is correct.

What it does

Every project gets an automatic address under the platform's own domain, such as my-app.stackap.com, as soon as it is created. That is the address to use for testing and for a staging copy.

For a real domain, you add the hostname with stackap domains add <slug> <host>. The reply includes an instruction in the form of an A record: the name to create and the server's IP address to point it at. Stackap does not edit your DNS, because it is hosted with a different company, and it does not need to.

Stackap checks that the name really resolves to the server before it asks for a certificate, and it reports two separate states for each hostname: the DNS status and the certificate status. Certificates are issued and renewed automatically by the web server in front of the apps.

How it works

Attach the hostname to the project. The API returns the record to create.
Create the A record at your DNS provider. Lower its cache lifetime a day before any production switch so a change takes effect quickly.
Listing domains refreshes the status. When DNS resolves, the certificate is issued and traffic is routed to the project.
A monitor check reads the certificates actually being served and warns as they approach expiry.

A hostname can only be attached to one project, and a request to attach one that is taken, or that would shadow another project's automatic address, is refused with the same response either way. The platform operator can additionally attach names under the platform's own base domain.

In practice

$ stackap domains add my-app www.example.com
$ stackap domains ls my-app
$ stackap domains rm my-app www.example.com

Early-access scope

The DNS record is yours to create, by hand, at your DNS provider. Stackap never changes DNS and says so.
The instruction is a single A record to one server address. There is one server, so there is no failover address behind it.
A bare domain redirecting to www, or the reverse, is configured per project and is not a one-click setting.
Stackap is not a domain registrar and does not host email.

Questions

How long until HTTPS works?

As long as it takes your new DNS record to propagate, plus a short wait for the certificate. We have not measured a typical time because propagation depends on your provider and the record's cache lifetime.

Can I move a live domain with no downtime?

Run the new site on its automatic address, compare it with the old one, and then change the single DNS record. Lowering the record's cache lifetime a day earlier makes the change land faster.

Stackap is in early access. Tell us what you run and we will reply with a straight answer about whether it fits.

Ask for an invitation

Last updated 2026-10-03.