BWEZE as a registrar (EPP)
How BWEZE registers domains directly with registries over EPP - RICTA's .rw registry first - and what it takes to go live.
Most platforms resell domains through a third-party registrar's HTTP API. BWEZE
goes one level deeper for .rw: it speaks EPP - the Extensible Provisioning
Protocol - directly to the registry. That means a .rw domain you buy through
BWEZE is created at the registry by BWEZE acting as an accredited registrar, not
proxied through a reseller.
What EPP is
EPP is the standard registry protocol (RFC 5730, with object mappings for
[domains 5731], [contacts 5733], and [hosts/nameservers 5732]) carried over a
TLS-secured TCP transport (RFC 5734). A registrar opens a session, logs in with
its credentials, and exchanges XML commands - check, info, create,
update, renew, transfer, delete - against the registry's objects. Each
message is length-prefixed on the wire; every command gets a result code, where
anything >= 2000 is an error.
BWEZE ships its own EPP client, so there's no third-party dependency between the control plane and the registry.
Which registries
| Registry | TLDs | Transport | Status |
|---|---|---|---|
| RICTA | .rw, .co.rw, .org.rw, … | EPP over TLS | first target |
| others | .com, .app, .io, … | reseller API | via provider adapter |
Non-.rw TLDs still register through a provider adapter - EPP is the direct
path we use where BWEZE is (or is becoming) the accredited registrar.
The domain lifecycle
You never write EPP XML yourself. You use the same domains API/CLI/platform as
any other domain (see Domains); BWEZE translates to EPP under
the hood for .rw.
- check - availability.
GET /v1/domains/search(or the.rw-specificGET /v1/domains/rw/{name}) maps to EPPdomain:checkwhen the registry is configured, falling back to RDAP otherwise. - create -
POST /v1/projects/{id}/register-domainmaps to EPPdomain:create. BWEZE first ensures the contacts exist - the buyer as registrant and admin contact, BWEZE as tech contact (it runs the nameservers) - and the BWEZE nameserver host objects, then creates the domain in the buyer's name, delegated to those nameservers. Each set of owner details gets its own registry contact. - renew -
domain:renewfrom the current expiry. - transfer -
domain:transfer(request / query / approve / reject / cancel) using the domain's authInfo. - delete -
domain:delete.
Every .rw domain BWEZE registers is delegated to BWEZE's own authoritative
nameservers:
ns1.bweze.com
ns2.bweze.comBecause BWEZE controls that DNS (PowerDNS), a domain you buy is connected to your project and routed automatically - no manual DNS step.
Going live - operational prerequisites
The EPP path is config-gated and off by default. BWEZE is not yet an
accredited .rw registrar; enabling real registration requires:
- RICTA registrar accreditation. BWEZE must complete RICTA's registrar accreditation (the RICTA registrar opportunity) to receive production EPP credentials.
- OT&E credentials first. Registries issue Operational Test & Evaluation
(OT&E / sandbox) credentials to validate the integration before touching
production. Point
EPP_RW_HOSTat the OT&E endpoint until certified. - Public nameservers.
ns1.bweze.com/ns2.bweze.commust resolve to stable public IPs running PowerDNS. For.rwthey are hosts outside the registry's own zone, so no glue is needed there: ordinary A records inbweze.comare enough. Glue matters for.com/.netdomains, andbweze.com's registrar cannot add it today (infra/NAMESERVERS.md). - Credentials in the control plane. Set
EPP_RW_HOST,EPP_RW_CLID,EPP_RW_PW, and the mutual-TLS material (EPP_RW_CLIENT_CERT,EPP_RW_CLIENT_KEY,EPP_RW_CA) in theapps/webenvironment.EPP_RW_TECH_CONTACT_IDnames BWEZE's own contact (defaultBWEZE).
Until all of that is in place, .rw availability answers over RDAP and a
purchase records a requested registration that BWEZE fulfils manually - the
API surface is identical either way. The buyer pays up front in both cases; a
registration the registry refuses, or that BWEZE cannot complete by hand, is
refunded in full.