Languages

Neens ships its interface in eight languages, and every one of them is fully translated — not “mostly”. This page covers how to choose yours, how an API client asks for a language, and what stays in English on purpose.

At a glance

Supported languages

Picking Arabic sets the document direction to RTL, so text, input fields, and the browser’s own scrollbars and text selection follow Arabic reading order.

Choose your language

Ask for a language from an API client

Every JSON API route honours the standard Accept-Language request header. The web app stamps your active language on every call it makes; your own scripts and integrations can do the same.

# German error copy from a deliberately unauthenticated call
curl -s https://app.neens.ai/api/auth/me \
  -H 'Accept-Language: de'
# {"detail":"Nicht authentifiziert."}
 
# Same call, Japanese
curl -s https://app.neens.ai/api/auth/me \
  -H 'Accept-Language: ja'
# {"detail":"認証されていません。"}

import httpx
 
client = httpx.Client(
    base_url="https://app.neens.ai",
    headers={
        "Authorization": "Bearer nk_live_…",
        "Accept-Language": "fr",
    },
)
r = client.get("/api/sessions", params={"limit": 20})

const res = await fetch('https://app.neens.ai/api/sessions?limit=20', {
  headers: {
    Authorization: 'Bearer nk_live_…',
    'Accept-Language': 'pt',
  },
})

Header handling follows the spec, so you can pass a browser’s header through unchanged:

What gets translated

What stays in English

Some strings are identical in every language on purpose, and translating them would make the product harder to use:

• The product name — Neens.
• Acronyms borrowed unchanged across all eight languages — API, SDK, LLM, URL, JSON, CSV, HTTP, IP, PR, CI, MCP, SSO, TOTP.
• Metric and verdict tokens that must match what the API returns and the CI runners print — pass^k, PASS, FAIL, p50/p95/p99.
• Code you would copy-paste — field names, file names, env var names, header names (X-Neens-Project-Id), span attributes (neens.*), key prefixes (nk_live_…), and model ids such as claude-opus-5.
• Vendor names — GitHub, Slack, ClickHouse, Postgres, Langfuse, Zendesk, and the rest.

The judgement calls — a word that happens to be identical in one language, a label that stays an acronym — are recorded one by one with a written reason. The purely mechanical cases (a bare number, a URL, an identifier like user_id) are recognised automatically and deliberately are not listed, so the recorded list stays short enough to actually read.

How completeness is guaranteed

A missing translation is easy to catch. A translation that is silently the English string is not: the language file has the key, everything loads, and only a reader who speaks the language notices. That is exactly what happened to one of our pre-production screens, whose sign-in hints sat in English across all seven non-English languages while every automated check reported green.

Neens now blocks both failure modes before a change can ship:

1. Every language carries every key. A key that exists in English and is missing elsewhere fails the build.
2. No language may carry the English string. If a value is byte-identical to the English one, it fails the build — unless it is on the short, reasoned list above, or it is structurally untranslatable (a bare number, a URL, an identifier like user_id, a {{placeholder}}).
3. Every language carries every plural form it needs. English has two (one/other); Arabic has six and the Romance languages have three. A language missing one of its own forms falls back to English for exactly the counts in that form — for Arabic that was 0 and 2–99 — so the build now checks each language against its own CLDR rules, not against English’s.
4. Nothing can be deferred quietly. The list of accepted exceptions can only shrink automatically; adding to it takes a deliberate, reviewed edit.

So “eight languages” means the same thing for the eighth language as for the first.

Troubleshooting

Related: Account settings · LLM connections