Founder Guide

Connect Your Own Domain (e.g. axomed.pk)

Step-by-step, non-technical. You need two things before starting: (1) access to your domain registrar (where you bought the domain — e.g. Namecheap, GoDaddy, Cloudflare, pknic) and (2) the ability to edit DNS records (A records / CNAME). No coding required.

Good news: you do NOT need to build anything new. The AXOMED frontend is already hosted (permanent URLs) and the backend is already running. Connecting a domain is just pointing your domain name at those existing servers using DNS.

Before you start — what you need

Option A — Point the domain to the AXOMED frontend (website)

This makes visitors who type axomed.pk see the AXOMED landing page + all portals.

Step 1 — Choose where the site is hosted

The AXOMED frontend is a set of static HTML files. Static hosting services that give you a clean custom domain (free or cheap):

ServiceWhat you getCost
NetlifyDrag-and-drop upload + custom domain wizardFree tier
VercelDeploy from folder + custom domainFree tier
Cloudflare PagesFast global CDN + free SSLFree tier
Teamily static hosting (current)Permanent URL, already liveIncluded

If you want axomed.pk exactly, Netlify/Cloudflare Pages are the simplest. We can push the v19 folder there for you in one step.

Step 2 — Create the DNS records (do this at your registrar)

In your registrar's DNS Management panel, add these exact records (these are Netlify's standard values — copy them as-is):

TypeName/HostValue/Points to
A@ (root, e.g. axomed.pk)75.2.60.5
CNAMEwwwaxomed-v19.netlify.app
Important: after adding these records, open Netlify → your site → Domain settings → Add custom domain, type axomed.pk (and www.axomed.pk). Netlify verifies the DNS and auto-provisions the SSL certificate (https://) — you don't need to buy or install any certificate yourself.

Step 3 — Add the domain in the hosting service

  1. Log in to Netlify/Vercel/Cloudflare Pages → your site → Domain settings.
  2. Click Add custom domain and type axomed.pk (and www.axomed.pk).
  3. They verify DNS (this takes a few minutes to 24 hours).
  4. SSL (https://) is enabled automatically.

Step 4 — Wait & test

DNS changes propagate in 30 minutes to 48 hours (usually under 2 hours). Then open https://axomed.pk — you should see the AXOMED landing page. If it doesn't work after 48h, send us your DNS panel screenshot and we'll spot the issue.

Option B — Point a subdomain to the AXOMED backend (API)

Optional — only needed when the backend is deployed to Railway with a real database. This gives you api.axomed.pk for the backend instead of the long Railway URL.

Step 1 — Deploy backend on Railway

Requires the Railway rly_ token + Supabase credentials (as discussed). Once deployed, Railway gives you a URL like axomed-production.up.railway.app.

Step 2 — Add the domain in Railway

  1. Railway → your service → Settings → Networking → Generate Domain (get the .up.railway.app URL).
  2. Click Custom Domain → enter api.axomed.pk. Railway shows you a DNS value to add.

Step 3 — Create the DNS record

TypeName/HostValue/Points to
CNAMEapiaxomed-production.up.railway.app
Note: Railway handles the SSL certificate automatically once the CNAME resolves.

Cheat sheet — all DNS records in one table

PurposeTypeNameValue
Website (root)A@75.2.60.5 (Netlify)
Website (www)CNAMEwwwaxomed-v19.netlify.app
Backend APICNAMEapiyour-service.up.railway.app

That's it — 3 records total. Everything else (email, etc.) can stay untouched.

What we can do for you: push the v19 frontend to Netlify/Cloudflare Pages with the custom domain already configured, prepare the exact DNS values for your registrar, and wire the backend subdomain once Railway is live. Just share your domain registrar login type (Namecheap / GoDaddy / Cloudflare / pknic) and we'll give you the exact copy-paste values.