Public roadmap

Roadmap

We are building AIvikings in the open. Here is what is live, what we are actively building, and where the platform goes after the registrar foundation.

Now

Live now

Built, running, and ready for real domain operations.

Production registration

Real domains can be registered through AIvikings, with availability, registration, nameservers, and status handled end to end.

Agent-native registrar

One core service, reachable over HTTPS, that registers and manages domains through a clean REST API and MCP tools.

Pricing and premium domains

Catalog, rules, premium and fixed TLD pricing, overrides, currency normalization, retries, and fallback logic keep pricing ready for real registrations.

Contacts and account defaults

Contact roles, registrant profile sync, stale-link repair, and default nameserver management are available for cleaner account operations.

Managed DNS

Full DNS record management is available for create, read, update, and delete workflows, with simpler relative record names and configurable default nameservers through MCP.

Self-serve API keys

Builders can create access without waiting for a manual key handoff.

Billing and accounts

Account and billing foundations are in place for paid production registration, renewal, and usage workflows.

Customer dashboard

A full self-service dashboard for API keys, account setup, domains, connection status, and operational workflows.

Expanded TLD coverage

A broader public TLD catalog with local cache, price-list pages, and individual TLD pages for discovery and SEO.

Public API reference and SDKs

Reference documentation and SDK groundwork for builders integrating AIvikings into agents and applications.

Rate limiting and abuse protection

Public endpoints include hardening work for safer access as real usage opens up.

Operational reliability

Logging, MCP health checks, API-key validation, and broader test coverage improve day-to-day platform resilience.

Ambassador program

A comprehensive ambassador program is live, with public program details and legal terms.

Later

Where we are headed

The longer-term direction.

Agent hosting

Run the agents you build elsewhere, with no terminal and no Docker. The next AIvikings layer extends the registrar foundation into hosted agent operations.

Premium DNS tier

Advanced Anycast, traffic steering, failover, and SLAs for teams that need more than the standard managed DNS layer.

Multi-tenant teams

Separate users, roles, accounts, contact handles, billing views, and policy controls for teams and resellers.

Domain transfers and aftermarket

Bring existing domains into AIvikings, then expand beyond new registrations into transfer and portfolio workflows.

Deeper agent integrations

First-class examples and patterns across MCP-compatible clients and popular agent frameworks.

Domain intelligence

Agent-friendly recommendations for naming, TLD choice, risk signals, renewal planning, and portfolio hygiene.

Have something you want on this roadmap? Tell us what you are building.

FAQ

Frequently asked questions

What does "Now / Next / Later" mean on this roadmap?

Now is what is built and running. Next is what is actively being prepared for broader production use. Later is the longer-term platform direction. AIvikings updates the roadmap as things ship.

Is live production registration available yet?

Yes. Production registration is available through AIvikings, with billing, accounts, API keys, contact handling, default nameservers, and managed DNS workflows in place.

Will AIvikings include DNS hosting?

Yes. Standard managed DNS includes full DNS record management and nameserver workflows across the dashboard, API, and MCP tools. A premium DNS tier with Anycast and SLAs remains a later item.

When can I get an API key?

Self-serve API keys, billing, accounts, account top-up, and the customer dashboard are in place. Builders can move from signup to first registration without a manual API-key handoff.

What is agent hosting on the roadmap?

A planned AIvikings product layer that lets you run agents you built elsewhere, with no terminal and no Docker. It remains a later item after the registrar, billing, dashboard, and managed DNS layers continue to mature.