A domain name is the web address of your college website (example: mamw.org). Each institution on the Sahasra Platform requires its own domain. There are two options depending on whether the college already has one.
The domain always remains the property of the institution. SahasraTechnologies does not take ownership of any domain. Only DNS configuration access is needed — this is just pointing the domain to our hosting servers, similar to how you point a phone number to a new address.
Once a domain is ready, it needs to be configured to point to our hosting servers. This is a one-time technical step done by either the institution's domain provider or by SahasraTechnologies with access.
| Method | What It Means | Who Does It | Time |
|---|---|---|---|
| Update A Record | Point domain directly to our server IP address | Institution via domain provider login, or us with access | 1–24 hrs propagation |
| Update CNAME | Alias subdomain (e.g. www) to our platform hostname | Institution via domain provider login, or us with access | 1–24 hrs propagation |
| Update Name Servers | Transfer DNS management fully to our name servers | Institution authorises, we configure | 24–48 hrs propagation |
We recommend updating only the A Record — this keeps all other DNS settings (email, subdomains) untouched and only routes the website traffic to the Sahasra Platform. The institution retains full DNS control at all times.
We need either: (a) login access to the domain provider portal (GoDaddy, BigRock, Hostinger, etc.) to configure DNS ourselves, OR (b) the institution's IT team can make the DNS change as per our instructions — we provide the exact values to enter (IP address or hostname).
After the domain is configured and pointing to our servers, the institution is provisioned on the platform. Each college gets a completely isolated environment — its own website, admin panel, and data.
The Sahasra Platform is multi-tenant. Think of it like an apartment building — one building (shared infrastructure), but each apartment (college) is completely private and independent. Tenants do not see each other's content, files, or data.
All existing website content is migrated into the Sahasra CMS. The institution reviews the new website on a test URL before the domain is switched over.
When the institution approves the new website, the domain's DNS is updated to point to the live platform (if not already done). Within 1–24 hours of DNS propagation, the new CMS-driven website is live at the institution's domain. The old website is retired.