Publish Extension Multi-DC
Summary
Multi-datacenter (Multi-DC) publishing enables your extension to be deployed across Zoho's global datacenters, making it available to users in different regions worldwide. Each datacenter requires a separate publish step.
Available Datacenters
| Datacenter | Region | Domain Suffix | Writer URL |
|---|---|---|---|
| US | United States | .com | writer.zoho.com |
| EU | Europe | .eu | writer.zoho.eu |
| IN | India | .in | writer.zoho.in |
| AU | Australia | .com.au | writer.zoho.com.au |
| JP | Japan | .jp | writer.zoho.jp |
| CA | Canada | .ca | writer.zoho.ca |
| SA | Saudi Arabia | .sa | writer.zoho.sa |
| CN | China | .com.cn | writer.zoho.com.cn |
Step-by-Step Guide
Step 1: Publish in Primary Datacenter (US)
- Build and test your extension in Sigma (US datacenter by default)
- Publish as Private or Public in the US datacenter
- Verify the extension works correctly
Step 2: Configure Per-Datacenter API Endpoints
Third-party API endpoints may differ per datacenter. Update your extension code to handle regional endpoints:
function getApiEndpoint() {
const hostname = window.location.hostname;
if (hostname.includes("zoho.eu")) return "https://api.example.eu/v1";
if (hostname.includes("zoho.in")) return "https://api.example.in/v1";
if (hostname.includes("zoho.com.au")) return "https://api.example.au/v1";
return "https://api.example.com/v1"; // Default US
}Step 3: Publish to Each Target Datacenter
For each datacenter you want to support:
- Log into the regional Sigma (e.g., sigma.zoho.eu for Europe)
- Import or recreate your extension
- Click Publish and select the publish type

- Complete publication for that region
Note: Each datacenter is independent. You must publish the extension separately in each target datacenter.
Step 4: Verify Regional Deployment
- Test the extension in Zoho Writer for each datacenter
- Verify API calls route to the correct regional endpoints
- Confirm compliance with regional data regulations
Compliance Considerations
| Datacenter | Regulation | Key Requirement |
|---|---|---|
| EU | GDPR | Data must stay within EU; user consent required for data collection |
| IN | PDPA (India) | Personal data must be stored within India |
| CN | PIPL (China) | Stricter data localization requirements |
| Others | Local laws | Follow applicable local data protection laws |
Best Practices
- Maintain a single codebase with environment-aware configuration
- Test in each datacenter before releasing to users
- Document which datacenters your extension supports
- Monitor for regional API differences or rate limits
- Check regional legal compliance before publishing