Getting started

Activate your account and sign in

Neens accounts are created by invitation. The first admin of a new company receives an activation email when the workspace is provisioned; everyone else is invited by a workspace admin from Settings → Members.

The email contains a one-time activation link (/activate?token=…). Open it, set a password (at least 12 characters by default, and not one that appears in public breach lists — the form states the exact rules) and optionally your display name, and you’re signed in immediately — no separate login needed the first time. Invitation links expire after 14 days; if yours has expired, ask an admin to resend it.

After that, sign in at /login with your email and password. If you’ve turned on two-factor authentication — required on operator accounts, optional for everyone else — sign-in asks for your 6-digit code as a second step, and a completed password reset asks for it too. Forgot your password? Forgot password emails you a reset link that’s valid for 60 minutes.

Work through the workspace checklist (admins)

The first company admin lands on the Getting started page — a five-step checklist that sets up the workspace. Only admins see it; you can complete it in any order, or Skip for now and return later via Getting started in the sidebar.

1. Name your workspace — rename the seeded default organization and agent to names your team will recognize (changeable any time).
2. Invite your team — teammates get a one-time activation link by email; assign each a role (admin, member, or viewer).
3. Connect an LLM — required for scoring and every other AI feature; see the next step.
4. Assign personas to your team — give each member a starting view tailored to how they work. A persona changes layout emphasis only, never access.
5. Set up trace tracking — hands off to the agent setup below.

Connect an LLM

Every AI feature — judge scoring, cluster labels, insight summaries, topic classification, enrichments, remediations, and the in-app assistant — runs on an LLM connection you configure. Neens ships with no built-in model access.

1. Open Settings → LLM providers and click to add a connection.
2. Pick an API format — Anthropic, OpenAI-compatible (which covers DeepSeek, Together, Fireworks, vLLM, and most gateways, plus a local Ollama), Google Gemini, or one of the other formats — then set the model, an optional base URL for compatible/local endpoints, and your API key.
3. Optionally scope it: a connection can be visible company-wide (default), or restricted to specific orgs or agents. Mark one as the default for its scope.
4. Use the connection test to verify it’s reachable — this makes one real (tiny) model call.

Credentials are encrypted at rest and never shown again after you save them.

Run agent setup

Everything in Neens lives inside an Agent (formerly called a Project) — traces, judges, datasets, and dashboards are all agent-scoped. Pick your agent from the agent switcher in the sidebar, then run the one-click agent setup (the Set up trace tracking checklist step, or Settings → Agent). It provisions, in one go:

• an ingest API key for the agent (shown once — copy it),
• three default judges plus the Primary Score composite, configured to continuously score a 5% sample of incoming traces,

and then tracks your first trace, first score, and first failure cluster as they happen.

Create an ingest API key

Agent setup already minted a key, but you can manage keys any time — for example a separate key per environment.

1. Open Settings → API keys.
2. Click create, give the key a name (e.g. production-ingest), and copy the value.

Keys are prefixed nk_live_ and each key is bound to exactly one agent: anything sent with it lands in that agent, and it can’t write anywhere else.

Send your first trace

Neens ingests standard OpenTelemetry traces — if your agent is already instrumented, just point the OTLP exporter at Neens and send your key as a bearer token.

export OTEL_EXPORTER_OTLP_ENDPOINT="https://<your-neens-host>"
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer nk_live_your_key_here"
# then run your agent as usual — spans export to Neens over OTLP/HTTP
python my_agent.py

curl -X POST "https://<your-neens-host>/ingest/raw" \
  -H "Authorization: Bearer nk_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "session": {"id": "trace-001", "agent_name": "my-agent"},
    "spans": [
      {"id": "span-1", "name": "llm.call", "kind": "llm",
       "input": "What is the capital of France?",
       "output": "The capital of France is Paris."}
    ]
  }'

Ingestion is asynchronous: Neens accepts the trace and returns 202 Accepted immediately, then processes it in the background. Add ?sync=true to the URL to process inline while you’re testing. For every supported format (OTLP, OpenInference, raw JSON, batch) and richer examples, see Send traces.

See it in Neens

Open Traces in the sidebar — your trace appears within a few seconds. Click it to inspect spans, tool calls, inputs, outputs, latency, and cost. Related traces that share a conversation are rolled up on the Sessions page (the conversation-level view) — see Traces & sessions.

If nothing shows up, work through the FAQ checklist.

Watch the first scores arrive

With an LLM connection configured, the Primary Score judge scores a sample of incoming traces automatically — open Scores to watch quality signal accumulate, or Judges to add more evaluators. See Continuous evaluation.