What are reliable alternatives to Openprovider for automated .ch domain registration?
Asked by
MellowCedar42
I'm building a SaaS that automatically registers domains for Swiss SMEs immediately after checkout, with no manual intervention. I'm testing Openprovider, but I've run into problems with its sandbox, API behavior, and domain registration flow, so I'm evaluating alternatives that are reliable enough for production.
The main requirements are a REST API for domain availability and registration, a usable sandbox, registrar-only services, the ability to specify nameservers during registration, and no large upfront deposit or monthly minimum. Webhooks for domain-status updates would also be helpful. DNS will be managed through Cloudflare and hosting through Vercel.
Which registrar or reseller are you using for automated registrations, especially for .ch domains? How dependable has the API been, and does it support fully hands-off registration and renewal workflows?
Answers
INWX is worth investigating for this use case, and Crazy Domains may also be an option, although deposit requirements could make it less attractive. For .ch specifically, verify that the provider has an actual production-grade EPP or API integration and explicitly supports creation, renewal, and transfer—not just availability checks. A polished sandbox is less important than reliable live operations.
Reply to this answer
I’d design the integration as an asynchronous workflow even if the registration endpoint responds immediately. Store an idempotency key and track states such as pending, registered, and failed. Then reconcile through webhooks when available, or polling when they aren’t. This protects you from duplicate registrations, timeouts, and cases where the domain is registered but a nameserver update fails.
Reply to this answer
A clean sequence is availability check, registration, and then nameserver reconciliation as separate idempotent steps. Persist each result and make retries safe. Also test renewals, transfers, rejected registrations, delayed status changes, and webhook drift in addition to the happy path. For this product, explicit .ch support and dependable recovery behavior matter more than having a feature-heavy sandbox.
Reply to this answer
Before switching providers, inspect the raw request and response with curl or your browser’s network tools. Confirm the HTTP status, response body, authentication headers, and the exact registration payload. Some apparent client or sandbox failures are caused by missing parameters or an unexpected API response, so this can quickly show whether Openprovider is actually rejecting the request or the integration is misreading the result.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions