New Voroa services get an onvoroa.com address: what changes
New Voroa services get a name.onvoroa.com address. Existing getvoroa.com addresses keep working as before and also answer on onvoroa.com. Nothing to do.
Every new web service and static site on Voroa now gets its free default address under onvoroa.com -
for example my-api.onvoroa.com - instead of getvoroa.com. Services created before this change keep
their getvoroa.com address, and it keeps working exactly as before. They also answer on the matching
onvoroa.com address. You do not need to change anything.
Why new services use onvoroa.com
Your service now lives on its own domain, separate from the domain that runs the Voroa dashboard and sign-in. That keeps the content of a customer’s service apart from Voroa’s own account pages.
What changes, by type of service
| Your service | What happens |
|---|---|
| Created on or after 4 November 2026 | Gets an onvoroa.com address. Nothing to do. |
| Created before 4 November 2026 | Keeps name.getvoroa.com, which keeps working. It also answers on name.onvoroa.com. |
| Uses a custom domain | Your custom domain keeps working exactly as before. |
| Background worker or cron job | Has no public address, so nothing changes. |
The onvoroa.com address of an older service uses the same name: my-api.getvoroa.com also answers
as my-api.onvoroa.com. A service that is stopped or asleep picks up its onvoroa.com address the next
time it starts or deploys.
Renaming a service’s subdomain gives it a new onvoroa.com address. See
How to change your service’s subdomain.
Should I switch an older service to the onvoroa.com address?
You do not have to. If you want to use the new address anyway, add it everywhere your app checks its own
host name - for example Django ALLOWED_HOSTS, Rails config.hosts, Vite allowedHosts, CORS origins
and sign-in (OAuth) callback URLs. Cookies belong to one address, so people signed in on one address sign
in again on the other.
Frequently asked questions
Will my getvoroa.com address stop working?
No. Existing getvoroa.com addresses keep working, for browsers, API calls and webhooks alike.
Will my service go down?
No. You do not need to redeploy.
Does my custom domain change?
No. A custom domain keeps working. Its CNAME record can stay pointed at the getvoroa.com address, or
you can point it at the onvoroa.com one.
Do I need to update links to my service?
No. Old getvoroa.com links keep working, so links already shared, bookmarked or saved in other
apps do not break.
What about webhooks that call my service?
They keep working on the getvoroa.com address. Change a webhook to the onvoroa.com address only if
you want to, and add that address to any allow-list your app checks first.
Can I use my own domain instead?
Yes. Add a custom domain with free HTTPS. See custom domains.
Does this cost anything?
No.