Novaya builds context infrastructure for AI agents — the code, data, and systems an agent works inside but was never trained on. It ships Nexus, an AI coding agent whose Codewiki layer turns a codebase into a living knowledge graph, and Novaya Enterprise, which builds the same kind of graph across an organization's operational data. Codewiki is also available on its own as an API that Claude Code, Cursor, Codex, and CI jobs can consume. The name is Slavic for new.

What is Novaya Enterprise?

Context infrastructure at the organizational level, previously called ACMS. It turns operational data — codebase, decisions, ownership graph, incident history — into a live knowledge graph with a self-building ontology that AI agents can reason over and act on. Not a database and not a search tool: the context layer that makes autonomous agents useful inside a company.

Codewiki turns a repository into a knowledge graph and serves it to any coding agent over one API. It stores four things that cannot be recovered by reading the files: the structure of the code including runtime relations no parser can see; the recorded reasoning behind every commit; the files that historically change together with no static link between them; and the architecture computed from all three — hubs, subsystems, layering, and cycles. It connects to Claude Code, Cursor, and Codex in one step as a native MCP memory server.

How is this different from grep, embeddings, or just reading the repository?

Grep and file reads answer what the code says right now, and they are excellent at it. Codewiki answers questions whose evidence is not in the current files at all: why this exists, what breaks if I change it, which files move together, and what the architecture actually became. Co-change coupling is the clearest example — two files that always ship together with no import between them is a fact that lives only in the history. Both kinds of retrieval are needed; they are not substitutes.

Does Novaya store my source code?

No. Indexing runs locally or in your CI, and only the derived graph projection is pushed. The hosted store has nowhere to put file contents — that is a property of the schema, asserted by a test, not a policy promise. Every answer is computed from the projection anyway, so custody of your source would buy nothing.

How is the Context API priced?

By connected repositories and seats — never by tokens returned. Metering on tokens returned would invert the incentives: Novaya would profit by sending your agent more context, which raises your inference bill, which is the thing the product exists to reduce. The first five connected codebases are free, and running Codewiki locally costs nothing.

What is Nexus, and why ship an agent if agents are the customers?

Nexus is Novaya's first-party coding agent. It exists to prove the context layer works and to supply enrichment the engine deliberately does not contain, such as the embedder and model-inferred relations. It reaches Codewiki only through the same public API any other agent uses, and it stays free and bring-your-own-key, so it never competes with the agents Codewiki sells into.

Which agents can consume the graph?

Anything that speaks the Model Context Protocol, plus REST and a CLI for everything else. Claude Code, Cursor, and Codex connect in one step and register Codewiki as a native memory server. CI jobs query the same API under a key.

What is a Codewiki Context API Key?

A repository-scoped credential that authorizes an agent or developer tool to read the contextual knowledge generated from one specific indexed codebase. Each key is bound to a particular repository and its Codewiki knowledge graph, so an authorized integration can retrieve structured code context, dependencies, architectural relationships, source references, and change history without needing to understand or manage the indexing infrastructure underneath. The key is the authentication layer between your agent environment and the Context API.

How do I manage, rotate, or revoke a Context API Key?

From the Novaya dashboard. Permissions, repository scope, usage limits, creation time, and status are all visible per key, and any key can be rotated in place or revoked outright. Both take effect immediately, affect only that key, and leave the repository's graph untouched — rotating a credential never means re-indexing a codebase. Because scope is the repository rather than the account, a leaked key exposes the context of one codebase and cannot reach your other repositories.

Novaya

Context infrastructure
for AI agents.

An agent is only as good as what it knows. Novaya connects AI agents to the data beyond the web and beyond training data — your private, operational context — and turns it into a living knowledge graph they can reason over.

Two products, one idea — context infrastructure at two scales.

Nexus

Context infrastructure at the developer level.

Agent infrastructure that turns your codebase into a living knowledge graph — the context a model was never trained on — and gets better at your work the more you use it.

Adapts to your workflow and remembers your decisions

Improves itself 24/7 — turns repeat tasks into skills

Codewiki plugs into Claude Code, Codex & Cursor in one step

One-click integrations — plus anything with an MCP server

Runs on your own device and your own API keys

Learn more ›

Enterprise