Partner framework

Packages and registrar modules

This is the partner-facing menu for what is included, what can be added, and what needs custom scope.

How To Read This

IncludedThe module is part of the package baseline when the partner is approved and launch-ready.

Paid add-onThe module can be enabled after pricing, support, and operational requirements are approved.

Custom scopeThe module needs written scope, package terms, or a support request before HeadlessDomains commits to delivery.

none source access

Hosted Starter

HeadlessDomains hosts and manages the registrar; partner requests changes through support.

Best pilot default when the reseller wants launch speed without repo access.

Included modules

Branded domain search Partner checkout handoff Customer domain dashboard

downstream_repo source access

Framework Partner

Partner gets a downstream white-label repo workflow while HeadlessDomains keeps backend secrets protected.

Use written package/license terms before granting repo access.

Included modules

Branded domain search Partner checkout handoff Customer domain dashboard Embeddable homepage search Downstream repo access

none source access

API-only

Partner builds and hosts their own frontend against HeadlessDomains APIs and Gems settlement.

Good for technical partners who do not need our hosted frontend kit.

Included modules

Branded domain search Partner checkout handoff

custom source access

Custom / Enterprise

Custom backend adapters, repo access, support, SLA, or special integration terms.

Requires explicit scope, pricing, and support boundaries.

Included modules

Branded domain search Partner checkout handoff Customer domain dashboard Custom design and pages Downstream repo access Agent-friendly features

Module Catalog

Branded domain search Core registrar · default included · Search and availability for approved namespaces on the reseller's registrar. Launch baseline for every white-label registrar.

Partner checkout handoff Core registrar · default included · Partner collects customer payment, then calls the Partner API after payment succeeds. Keeps HeadlessDomains out of reseller customer payment collection.

Customer domain dashboard Account · default included · Customer-facing list of registered domains and basic account state. Expected once real registrations begin.

Basic DNS management Account · default paid · Customer can view and manage simple DNS records through the reseller registrar. Depends on backend zone id and record safety rules.

Email delivery / Mailgun Operations · default included · Transactional email setup so customer login codes and support emails are delivered from the reseller brand. Required before real customers can sign in with email codes.

Embeddable homepage search Growth · default paid · Search widget for the reseller's main website that redirects checkout to the registrar subdomain. Good fit for Marcus once the registrar flow is stable.

Agent-friendly features AI · default custom · Agent manifests, SKILL.md links, agent registration flows, and automation-safe API docs. Borrow selectively from headlessdomains.com instead of cloning everything.

HeadlessDomains catalog namespaces Inventory · default paid · Permission to sell HeadlessDomains-owned namespaces such as .agent, .chatbot, or future launches. Requires explicit namespace permission and pricing approval.

Registrar analytics Operations · default paid · Sales/search/activity reporting for reseller-owned registrar operations. Useful after traffic exists; not launch-critical.

Downstream repo access Developer · default custom · Private repo access or contribution workflow for reseller/AI-agent customization. Should be tied to written package terms.

Custom design and pages Support · default custom · Custom landing pages, styling, copy, or feature requests managed through support. Use support requests for scope and pricing.

Source Access Boundary

Hosted Starter partners request changes through support. Framework Partner and Custom / Enterprise partners may receive downstream repo access under written terms. API-only partners receive API docs, examples, and API keys; source access is not automatic.

Secrets, backend credentials, wallet credentials, and production registry logic stay out of downstream partner repos.