2.2 Connecting a Custom Domain

You will need to connect your custom domain to our platform so that your project is accessible under your own brand. To do this, you have two options:

1. Point Nameservers to Our Cloudflare
2. Configure A Records Directly

2.2.1 Point Nameservers to Our Cloudflare

The recommended and easiest approach is to point your domain’s nameservers to our Cloudflare.

Steps:

1. Log in to your domain registrar account (where you purchased your domain).
2. Find the nameserver (NS) settings for your domain.
3. Once updated, we will handle all DNS configurations (including subdomains, redirects, security settings, etc.) on our side via Cloudflare.

Replace the current nameservers with the Cloudflare nameservers we provide.

Please contact our team to get the exact Cloudflare nameserver details you should use.

Advantages:

• Centralized DNS and security management are handled by our team.
• Simplifies setup; no need to manually create separate DNS records.
• Easier to manage future changes or additional subdomains.

2.2.2 Configure A Records Directly

If you prefer to keep your existing nameservers, you can manually set up A records.

Steps:

1. Log in to your DNS provider's management panel
   Access the control panel where you manage your domain’s DNS settings. This is usually available through the registrar where you purchased your domain (e.g., GoDaddy, Namecheap), or in Cloudflare if you're using it as your DNS provider.
2. Identify and remove old conflicting records
   Before adding new records, check for any existing A or CNAME records that might conflict with the new setup (for example, old records pointing to other IP addresses for @, admin, or api). Remove them to avoid routing issues.
3. Create A records for each required subdomain
   You need to create separate A records for:
   Investor Backoffice (main site) — usually on the root domain (e.g., example.com).
   Admin Panel — typically on a subdomain (e.g., admin.example.com).
   API endpoint — (e.g., api.example.com).
4. Save and confirm
   After adding the new A records, save the changes. It can take some time (up to 24 hours) for DNS changes to fully propagate globally.

Example A records

How to create a record:Name: This is the prefix for the subdomain (e.g., use admin for admin.example.com, or @ for the root domain example.com).Type: Choose A record.Value: Enter the IP address we provide.Save the record.

Important notes:

• Be sure to confirm the exact IP addresses to use with our team before configuring.
• Changes to DNS may take up to 24–48 hours to fully propagate worldwide.

2.2.3 What Happens after You Have Pointed Your Domain

After pointing your domain (either by NS or A record), notify our technical team. Our team will finalize SSL, routing, and any additional configuration on our side.

Once setup is complete, we’ll confirm that everything is working and provide you with a go-live notice.

2.2.4 How We Handle Regular Updates

All updates to your separate deployment (hosted on your own domain) are handled automatically through a secure deployment system.

• Automated Deployment Process
  The entire application codebase is deployed using automated scripts run by a secure deployment machine. This machine holds a sealed deployment key that is required for publishing updates. Importantly, our developers do not have access to this key – it is embedded in the deployment infrastructure and never exposed.
  
• No Developer Access to Your Infrastructure
  While our infrastructure can access your hosted version to apply updates, our developers themselves do not have direct access to your servers or environment. The deployment process is fully automated and isolated from manual intervention.
  
• Auditable Activity Logs
  Every interaction with your server is logged. These logs are stored securely on Amazon Web Services and can be provided to you at any time upon request. If any manual server access is ever required (e.g., for debugging or troubleshooting), we will only proceed after receiving your explicit approval in writing.

This approach ensures your deployment stays up to date while maintaining strict boundaries between your infrastructure and our team.