Data residency
Each Pingram account lives in one region. Logs, end-user records, API keys, notification setup, verified domains, webhooks, and phone numbers for that account stay in that region.
US, EU, and Canada are available on every plan, including free, at no extra charge.
| Region | Where data is stored | Dashboard | API |
|---|---|---|---|
| United States | United States | app.pingram.io | https://api.pingram.io |
| EU | Frankfurt, Germany | app.eu.pingram.io | https://api.eu.pingram.io |
| Canada | Montreal area | app.ca.pingram.io | https://api.ca.pingram.io |
Canada-region logs and end-user records stay in Quebec. See Quebec Law 25.
Moving an existing account
Pingram migrates an existing account to another region only for customers on the Enterprise plan. Email support@pingram.io to request that migration.
On Free and Paid plans, create a new account in the region you want and point your integration at it. The current account stays in its region, with its logs, users, and configuration.
Pingram migrates an account for you on the Enterprise plan. On Free and Paid plans, follow the steps below.
1. Create the account in the target region
Sign up on that region’s dashboard:
- United States: https://app.pingram.io/signup
- EU (Frankfurt): https://app.eu.pingram.io/signup
- Canada: https://app.ca.pingram.io/signup
2. Set up the new account
Recreate what the original account uses: notification types and templates, teammates, webhooks, billing, and inbound addresses. If you send SMS or voice, order numbers and complete sender registration on the new account.
3. Use the new API key
On the new account, open API Keys and copy the secret key (pingram_sk_...). A key from one region returns 403 from the API in another region.
4. Point your integration at the new region
Pass the new key and the region together.
import { Pingram } from 'pingram';
const pingram = new Pingram({ apiKey: 'pingram_sk_...', region: 'eu' // 'us', 'eu', or 'ca'});You can also call the regional host directly:
| Region | API | SMTP | MCP |
|---|---|---|---|
us |
https://api.pingram.io |
smtp.pingram.io |
https://mcp.pingram.io |
eu |
https://api.eu.pingram.io |
smtp.eu.pingram.io |
https://mcp.eu.pingram.io |
ca |
https://api.ca.pingram.io |
smtp.ca.pingram.io |
https://mcp.ca.pingram.io |
For the CLI:
pingram login --key pingram_sk_... --region euIn Zapier and GitHub Actions, set the region to the value shown on the new account’s API Keys page (us, eu, or ca).
5. Verify sending domains again
Domain verification belongs to one account. Add the domain on the new account and publish the DNS records it shows you. See Domain Verification.
When sends are going through the new account, you can leave the original account in place. Its history stays on that account.