Summary / When to Use This
You can customize the web address your customers use to access their OnRamp portal. By default, your portal lives at companyname.portal.onramp.us
. If you’d like a branded link—like go.yourcompany.com
—you can set up a custom subdomain for a seamless customer experience.
Before You Begin
You’ll need access to your domain registrar (e.g., GoDaddy, Google Domains, Amazon Route 53, Network Solutions, etc.).
Make sure you know which subdomain you want to use (such as
onboard.yourcompany.com
).DNS changes may take a few hours to propagate once you update records.
Steps to Follow
1. Decide on your branded subdomain
Pick a short, clear subdomain that fits your customer experience. Examples include:
go.yourcompany.com
onboard.yourcompany.com
welcome.yourcompany.com
launch.yourcompany.com
2. Add a CNAME record in your domain registrar
Log in to your domain registrar account.
Add a new DNS record of type CNAME.
For the host/subdomain, enter the branded subdomain you chose.
Point the CNAME record to:
custom.onramp.us
.
This tells the internet to direct your chosen subdomain to OnRamp’s portal system.
3. Review special cases
Using Cloudflare? Be sure the CNAME record is set to “DNS only” (not proxied). If your setup requires proxying, contact OnRamp Support.
Have a CAA record? You may need to temporarily disable it while OnRamp provisions your SSL certificate, or add our SSL issuer (available from Support) to your CAA record.
4. Contact OnRamp to finish setup
Email support@onramp.us with the subdomain you’ve configured. Our team will finalize the setup and enable SSL for your branded portal.
Tips & Troubleshooting
Propagation delays: DNS changes can take up to 24 hours. If your link doesn’t work right away, give it time.
SSL errors: If you see a certificate error, it usually means the SSL certificate hasn’t finished provisioning yet. Contact Support if it persists longer than a few hours.
Testing: You can test whether your DNS is configured correctly by running a CNAME lookup for your chosen subdomain. It should point to
custom.onramp.us
.