Pricing

Choose how deeply you want AI to verify engineering work.

Undes is built for tasks where a fast AI answer is not enough: code review, architecture decisions, bug investigation, CI checks, and long-running engineering analysis.

Community

For first tests, local experiments and individual evaluation.

$0 / month
Start free
  • Public npm package: @undes.ai/cli
  • BYOK support
  • Basic multi-agent runs
  • Operator-facing result artifacts
  • Community updates

Team / Enterprise

For organizations evaluating Undes beyond individual Pro usage.

Contact us scope discussed separately
Contact us
  • No public self-service package yet
  • No public installation path yet
  • Scope and access discussed directly
  • Commercial terms by agreement

BYOK by design

Undes works with your own AI provider keys. Community focuses on OpenAI, Anthropic and Google. Pro is the paid track for a broader provider matrix.

Community is public

The Community package is publicly installable from npm. It is intended for initial evaluation, local experimentation and understanding the Undes workflow.

Pro is licensed

Pro uses a separate licensed package for professional workflows: history, inspection, exports, provider expansion and local-model support as those capabilities ship.

Expanded providers

The Pro provider-expansion track covers OpenAI-compatible endpoints such as OpenRouter, NVIDIA NIM and generic gateways, plus local model servers like Ollama, LM Studio and llama.cpp.

Built for verification

Some Undes runs can take longer than a normal assistant response. That is intentional: the product is optimized for evidence, critique, consensus and reviewable output.

Paddle checkout

Paid subscriptions will be processed through Paddle. Billing, invoices, taxes, subscription management and refund flows may be handled through Paddle checkout and receipts.

Organization discussions

Team and Enterprise usage is not packaged as a public self-service plan yet. Contact us if you want to discuss organizational requirements.

Common questions

Does the price include AI model tokens?

No. Undes is BYOK-first. You provide your own AI provider API keys, and model usage is billed by your selected AI provider according to their terms. The Community package is public, while Pro uses a separate licensed package.

What is the difference between Community and Pro?

Community is the public package for first tests and local experimentation. Pro is a separate licensed package intended for regular professional usage, session-aware workflows, run history, engineering memory, richer inspection, expanded provider support and email support.

Can I use OpenRouter, NVIDIA NIM, Ollama or LM Studio?

Community is intentionally limited to first-party cloud providers: OpenAI, Anthropic and Google. OpenAI-compatible aggregators, hosted NIM endpoints, local model servers and generic gateways belong to the Pro provider-expansion track. Exact availability depends on the licensed package version and model qualification status.

Why is Pro a separate package?

Licensed packages make it easier to separate public evaluation from commercial functionality, license activation and support scope.

Can I use Undes in CI/CD?

Yes. Undes is designed for workflows where analysis may run in the background: scheduled jobs, code review checks or CI/CD verification. For organization-wide usage, contact us first so the scope can be discussed directly.

Is there an on-premise option?

There is no public on-premise package or installation path yet. Organization-specific requirements can be discussed directly, but no deployment model is promised on this page.

Can I cancel a subscription?

Yes. Subscription cancellation stops future renewals. Refunds and billing questions are handled according to the Refund and Cancellation Policy and applicable checkout terms.

Which plan should I start with?

Start with Community if you want to test the concept. Choose Pro if you plan to use Undes regularly for real engineering tasks. Contact us if you are evaluating Undes for a team or organization and need to discuss scope.

Start with a real engineering question.

The best first test is not a toy prompt. Use a small real bug, architectural concern, or pull request where the final answer must be checked before merge.