Skip to content

Custom Domain Setup

Scope: Putting CampusCore on your own web address (like ai.university.edu), with HTTPS.

By this point the decision is already made. During the initial deployment you chose your custom domain and how HTTPS is handled - CampusCore-managed SSL or self-managed SSL - because those are part of the deployment configuration. This stage is simply putting that choice into effect, and how it goes depends on which you chose.

The one thing you'll do here is add a DNS record, so you'll need someone who can manage DNS for your domain (usually your IT or web team).

  1. We provision the certificate. During deployment, CampusCore requests and validates an HTTPS certificate for a subdomain we manage (yourname.campuscoreai.com). This is a one-time wait of roughly 30 to 45 minutes on the first deployment - no action from you.

  2. You add one DNS record. Once deployment finishes, we give you the exact target and you create a single CNAME:

    ai.university.edu   ->   yourname.campuscoreai.com

  3. You're live. HTTPS is configured end to end - there's no certificate for you to buy, install, or renew.

Using Cloudflare for DNS? Set the SSL mode to Full or Full (strict), since CampusCore already serves HTTPS.

If you chose self-managed SSL

You handle HTTPS yourself - for example, terminating SSL at Cloudflare or your own load balancer. You point your domain at the CampusCore load balancer, and your CampusCore contact confirms the exact target to use.

After it's set up

  • With CampusCore-managed SSL, the certificate auto-renews - there's nothing ongoing for you to maintain.
  • All traffic is encrypted in transit, and the application redirects any plain HTTP request to HTTPS.

Next: SSO Setup.