Choosing a Subdomain: .io, .dev, .de, .org and .ai

TL;DR — Language-model bots start by default on .zeptix.io, coding bots on .zeptix.dev. Further roots can make sense depending on the purpose. .zeptix.ai is intended as a premium option for business cases.

Concept

The domain is a signal to users. .zeptix.io looks general and is suited for classic chatbots, support, advice and knowledge bots. .zeptix.dev fits coding bots, developer tools, script generators and technical assistants. .zeptix.de makes sense when you want to appear strongly German-speaking. .zeptix.org fits communities, associations and open projects more. .zeptix.ai looks especially high-end and is reserved for business cases.

Concrete Steps

• Choose .io when your bot explains knowledge.
• Choose .dev when your bot generates code.
• Choose .de when the German target audience is in focus.
• Choose .org when community or organization matters.
• Choose .ai when you are a business and need a premium AI domain.

For Advanced Users

The root does not alone determine the bot type. A coding bot stays a coding bot through its bot type, not through the domain. The domain only helps users place the expectation correctly. That is why the name should also be clear, for example fivem-builder.zeptix.dev instead of hilfe.zeptix.dev.

Examples of Fitting Names

A classic support bot can be called hilfe.zeptix.io or support.zeptix.de. A coding bot should rather be called fivem-builder.zeptix.dev, python-helper.zeptix.dev or script-studio.zeptix.dev. A business team with a premium presence could later choose a .zeptix.ai variant if plan and positioning fit.

Why Wildcards Matter for Users

For users, what counts is that a newly created subdomain appears reachable immediately. For this, Zeptix uses, alongside specific tenant entries, a stable domain setup, so that new bots do not run empty because of DNS in-between states. As an owner you do not have to worry about this. What matters is only to choose the right root and a clear slug.

Root Is Not Identity

The identity of the bot is created through the bot type in Zeptix. A coding bot stays a coding bot, even if it exceptionally does not run on .dev. Conversely, a language-model bot does not become a coding bot just because it uses a technical domain. The domain only supports the users' expectation.

Acceptance Check

Before you use this bot publicly, ask yourself three questions: Does a new user immediately understand what the bot is meant for? Is there enough of your own training so that the bot does not answer only generically? Can you review the generated result before you pass it on? If any answer is no, you should keep testing the bot privately.

A good coding bot is not the bot with the longest answer. A good coding bot delivers a fitting, reviewable and transportable foundation. That is exactly why profile, snippets, domain, Credits and Artifact download are not separate topics. Together they form the product quality.

Domain Strategy for Multiple Bots

When an owner runs multiple bots, the domain strategy should be consistent. A product support bot can stay on .zeptix.io, a developer bot on .zeptix.dev, a German community on .zeptix.de and a premium AI offering on .zeptix.ai. This order helps users understand the role of the bot even before the first chat.

Business-Only at .ai

.zeptix.ai should be used deliberately. The domain looks more like a high-end AI product and should therefore not be open to every test bot. For business owners it can make sense when the bot is publicly advertised, multiple teams are involved or the AI character is part of the brand.

No Worries About Technology

Owners do not have to set DNS entries when they use the Zeptix roots. Zeptix handles routing, certificates and delivery. What matters is only to choose the right root during onboarding and to check in the dashboard whether the link is communicable the way users should later see it.