How do I connect a custom domain to my VeloCMS blog?
Add your subdomain in /admin/settings, point a CNAME at proxy.velocms.org, and Cloudflare auto-provisions the SSL cert in 1-5 minutes.
To connect a custom domain to your VeloCMS blog, simply navigate to the /admin/settings page in your dashboard, enter your preferred web address, and point a CNAME record from your domain registrar directly to proxy.velocms.org. Keep in mind that since we recently retired our free tier, you will need an active Pro, Business, or Agency plan to access this functionality.
What kind of web addresses are currently supported?
Right now, you can link up any standard subdomain to give your AI-first Next.js blog that polished, professional vibe. Think along the lines of www.yourwebsite.com or something more specialized like blog.yourbrand.com. If you were hoping to use a naked apex domain (meaning just yourwebsite.com without any prefix), you will have to hold tight for a little while longer. We haven't rolled out apex domain support in our current MVP phase just yet. Here is a quick, actionable tip for you: log into your domain provider and set up a basic URL redirect that forwards your naked domain straight over to your "www" address. That way, if a reader forgets to type the prefix, they still land exactly where they need to be without encountering an error page.
Where do I find my DNS records and get verified?
The entire setup process happens directly inside your VeloCMS admin dashboard. You absolutely do not need to go sign up for your own Cloudflare account to make this work, because we handle all that heavy lifting under the hood! Once you type your chosen subdomain into the settings panel, our system generates a specific target for you. You just need to jump over to wherever you bought your web address (like Namecheap, GoDaddy, or Hover) and create a new CNAME record pointing directly to proxy.velocms.org. After saving that tweak at your registrar, bounce back over to your VeloCMS tab and click the "Verify Now" button. Hitting that button forces our servers to refresh your status immediately. While DNS propagation used to be a notorious headache that took an entire weekend, our modern architecture usually clears the whole process in a speedy one to five minutes.
Do I need to worry about security or manual SSL certificates?
You can completely cross SSL configuration off your technical to-do list! Because VeloCMS utilizes an enterprise-grade Cloudflare for SaaS architecture in the background, robust security is baked right into the connection from day one. The exact second your DNS changes finish propagating across the internet, Cloudflare automatically provisions and attaches a brand new Let's Encrypt SSL certificate to your blog. There is no need to generate confusing encryption keys, copy-paste weird text blobs, or set calendar reminders to renew your certificate next year. It genuinely just works behind the scenes, ensuring your readers see that comforting little padlock icon in their browser right out of the gate.
What happens if I change my mind and disconnect the address?
Sometimes your digital strategy shifts (maybe you decide to completely rebrand or launch a totally different project!), and unlinking an old address is just as painless as setting it up. If you decide to sever the connection from your admin settings, your hard work won't suddenly disappear into the void. Instead, the CMS smoothly catches the fall and instantly reverts your entire blog back to its original .velocms.org subdomain. Your PocketBase database stays completely intact, all your AI-generated posts remain safely published, and you can easily map a brand-new custom address whenever inspiration strikes.
Running a modern publication shouldn't require a degree in server management. We designed this routing flow to be as frictionless as possible so you can get back to doing what actually matters: publishing great content. If you happen to run into any stubborn DNS hiccups along the way, just double-check that your registrar hasn't accidentally added extra periods to your CNAME target!