Hostnames

What lives at which hostname. It exists because our estate has three quite separate faces — consumer marketplaces, professional tools, and internal engineering sites — and knowing which one you are looking at tells you which codebase and which team you need.

Production is an inventory; non-production is a convention

The production hostnames were confirmed on 2026-09-03 from the organisation’s own code and the public almamobility.fi product listing. The non-production pattern below is the naming convention, and not every name it produces exists yet — see What resolves today.

Consumer marketplaces

Hostname	Vertical	Served by
nettiauto.com	Cars	nettix-web
nettimoto.com	Motorcycles	nettix-web
nettivene.com	Boats	nettix-web
nettikaravaani.com	Caravans	nettix-web
nettikone.com	Heavy machinery	nettix-www
nettivaraosa.com	Vehicle parts	nettix-www

The glossary owns which codebase serves which vertical; this table repeats it only because the pairing is the thing you want when you have a hostname in front of you.

Professional and dealer tools

The other half of our business, and the part engineers working only on the marketplaces tend not to know exists.

Hostname	What it is
app.nettixpro.fi	NettiXPro — the professional vehicle sales platform, built from the aso-* repositories
teho.nettix.fi	TEHO — the customer webstore and self-service purchasing tool, served by nettix-webstore

Hostnames on netwheels.fi are Netwheels products and belong to Systems & Insights, a different unit — see the glossary. They are listed publicly at almamobility.fi and are not documented here.

APIs

Hostname	Serves	Repository
api.nettix.fi	The REST API behind the marketplaces	nettix-api

Internal engineering sites

All behind Cloudflare Access, so an Alma identity is all you need.

Hostname	What it is	Source
docs.ajomark.dev	This site	docs.ajomark.dev
scorecard.ajomark.dev	Supply-chain dashboard. Cloudflare Access, then Auth0	security-dashboard
storybook.ajomark.dev	Shared component Storybook, published by the deploy-storybook workflow	ajomark-header and others

If one of these lets you in and another does not, that is an Access policy question, not a credentials question.

Non-production and feature environments

Every non-production marketplace hostname sits under ajomark.dev and follows one pattern, with the most specific part on the left:

{branch}.{environment}.{service}.{marketplace}.ajomark.dev

Drop the parts that do not apply. Test omits its environment name, so a bare {marketplace}.ajomark.dev is the test environment. No marketplace has an ajomark.dev name in production: it uses the marketplace’s own .com domain. The internal engineering sites above are the exception — they are production and they do sit under ajomark.dev. With Nettiauto and its messaging service as the example:

Environment	Main site	Sub-service
Feature	ajomark-1234.feature.nettiauto.ajomark.dev	ajomark-1234.feature.viestit.nettiauto.ajomark.dev
Test	nettiauto.ajomark.dev	viestit.nettiauto.ajomark.dev
Staging	staging.nettiauto.ajomark.dev	staging.viestit.nettiauto.ajomark.dev
Production	nettiauto.com	viestit.nettiauto.com

The rows hold for every vertical: swap nettiauto for nettimoto, nettivene, nettikaravaani, nettikone or nettivaraosa. What each environment is for, and who uses it, is on the Environments page.

Part	Is	Values
{branch}	The branch’s Jira key, lowercased. Feature environments only	The key and nothing else, such as ajomark-1234 — not the full branch name. No dots; they conflict with DNS.
{environment}	Which environment	feature or staging. Omitted for test
{service}	A sub-service, whose name sits directly left of the marketplace. Omitted for the main site	viestit, oma, api, hinnoittelu
{marketplace}	The vertical	nettiauto, nettimoto, nettivene, nettikaravaani, nettikone, nettivaraosa

The branch sits leftmost because wildcard DNS covers only the first label. Each feature branch gets its own isolated environment, deployed automatically from the branch, and every non-production hostname is behind Cloudflare Access rather than basic auth.

Sub-services

A sub-service is one whose name sits directly left of the marketplace in the hostname. That is a statement about the URL, not about the codebase — what stack each one runs on, and whether it is shared or per-vertical, is on Repositories.

Service	Is	Repository
viestit	Viestit — messaging	inbox
oma	OmaAjo — personal vehicle management	my-vehicles
api	The vertical’s API	—
hinnoittelu	Hinnoittelu — the pricing tool	pricing-tool

The glossary decodes the Finnish names.

Rekkari

Rekkari is not a vertical, so it takes the marketplace’s slot itself and has its own production domain. Its sub-services follow the standard extended pattern.

rekkari.com and api.rekkari.com come from this convention rather than from the 2026-09-03 production sweep above, so treat the two production rows below as inferred until someone confirms them.

Environment	Rekkari	A Rekkari sub-service
Feature	ajomark-1234.feature.rekkari.ajomark.dev	ajomark-1234.feature.api.rekkari.ajomark.dev
Test	rekkari.ajomark.dev	api.rekkari.ajomark.dev
Staging	staging.rekkari.ajomark.dev	staging.api.rekkari.ajomark.dev
Production	rekkari.com	api.rekkari.com

What resolves today

The pattern is the convention, not an inventory of what exists. On 2026-09-03 the test-level names for nettiauto, viestit.nettiauto and rekkari resolved, while staging.nettiauto.ajomark.dev and oma.nettiauto.ajomark.dev did not. Check before you send someone a link that fits the pattern:

dig +short staging.nettiauto.ajomark.dev

almaajo.dev is deprecated. It was the previous non-production domain and ajomark.dev has replaced it entirely, so treat any *.almaajo.dev name you meet in old configuration as a leftover rather than a target.

This page took the domain naming schema over from Confluence ALMA on 2026-09-03 and is now the authority. The Confluence page is the older copy.