Back to software engineering projects
Integrations case study
Custom Name Domain
A full-stack portal for purchasing domains, managing subscriptions, provisioning branded email, automating DNS, and accessing webmail.
Architecture map
Domain, email, billing, and provisioning workflow
Client experienceService boundaryData workflow
Business problem
Domain purchasing, recurring billing, DNS setup, and business-mail provisioning crossed several vendors and required dependable state coordination.
Architecture
Coordinated registrar, billing, DNS, and mail-provider operations through explicit provisioning stages, webhook-aware subscription state, scheduled work, and secured mailbox access.
My contribution
- Introduced Name.com availability, registration, pricing, order, DNS, renewal, and auto-renew operations on top of the existing registrar foundation.
- Built Stripe checkout and subscription flows for startup fees, plan changes, saved payment methods, webhooks, cancellation, reactivation, and transaction history.
- Automated staged Zoho Mail onboarding from domain registration through CNAME, MX, DKIM, IMAP, and active mailbox state.
- Built mailbox creation, administration, password, reactivation, encrypted credential, and tokenized webmail workflows.
- Extended the React portal with domain, billing, transaction, mailbox, export, dashboard, and responsive product experiences.
Difficult technical decisions
- Model provisioning as explicit stages instead of one long request so registrar, DNS, billing, and mailbox failures could be retried without repeating completed work.
- Treat vendor responses and Stripe webhooks as authoritative inputs while keeping a local state model that the product and support workflows could understand.
- Extend the existing GoDaddy product incrementally rather than rewriting proven paths, keeping contribution boundaries and migration risk clear.
Scale and constraints
- Five vendor boundaries: GoDaddy legacy paths, Name.com, Stripe, Zoho Mail, and Brevo.
- Seven registrar operations covering availability, registration, pricing, ordering, DNS, renewal, and auto-renew.
- A staged domain-to-mailbox lifecycle spanning domain registration, DNS verification, MX/DKIM configuration, IMAP readiness, and activation.
Security, performance and reliability
- Protected mailbox credentials with encryption and exposed webmail through short-lived tokenized access rather than reusable secrets.
- Used scheduled reconciliation and webhook-aware state to keep long-running provider work out of interactive requests and make partial failures recoverable.
- Kept vendor-specific logic behind service boundaries so retries, diagnostics, and future registrar changes remained localized.
Measurable result
- Combined five vendor systems and seven registrar operations into one repeatable self-service commerce and branded-email workflow.
- Moved mailbox onboarding from disconnected provider steps to an observable staged lifecycle with recoverable transitions.
What I learned
- Multi-provider automation becomes reliable when every external side effect has a named state, a retry boundary, and an operator-visible recovery path.
- The safest modernization path is often to preserve working legacy behavior while introducing clearer service boundaries around new capabilities.
Implementation stack
Technologies grouped by responsibility.
Frontend
ReactViteRedux Toolkit
Backend/CMS
Node.jsExpress.jsJWTnode-cron
Data
MongoDB
Integrations
StripeName.comZoho MailBrevoGoDaddy (legacy paths)
Related work