FIG. 1 - OPEN SOURCE Open client edges / managed engine
Answer-first OSS split

Open at the edge. Managed at the memory layer.

Answer Engine is open where developers need inspectable client edges: the MCP server and CLI packages. The hosted engine, indexes, billing, and evaluation systems are managed infrastructure. That split lets teams audit the install surface without pretending the entire memory service is an open-source project.

INSTALL SURFACE npx answer-engine-mcp ae sync run @answer-engine/mcp-server @answer-engine/cli
Available now @answer-engine/mcp-server package@answer-engine/cli packageClient-edge install contracts
Shipping next Registry listings Separated public repos Eval harness release decision
Fig. 2 honest split / no implied engine OSS
FIG. 2

Open vs managed

The split is explicit because developer trust breaks when the word open-source quietly expands past the code that is actually available to inspect.

Open

Thin client edges

  • @answer-engine/mcp-server
  • @answer-engine/cli
  • Install command and client wiring
  • Public repository split tracked for launch follow-up
Managed

Hosted memory infrastructure

  • Engine and retrieval/index services
  • Billing and credit enforcement
  • Hosted tenant data plane
  • Evaluation systems until release criteria are met
Fig. 3 managed service boundary
FIG. 3

The engine is not open

Answer Engine does not imply that the hosted engine, index, billing, or eval system is open source. Those are managed surfaces of the service.

BOUNDARY

Open-source means the MCP server and CLI edge packages are visible. It does not mean the managed memory engine, vector/index layer, credit system, or evaluation infrastructure is published as an open-source service.

Fig. 4 crawlable OSS answers
FIG. 4

FAQ

These answers are rendered as static HTML for evaluators and answer engines.

Is the Answer Engine service open source?

No. The MCP server and CLI are the open client edges. The hosted engine, indexes, billing, and evaluation systems remain managed infrastructure.

What can developers inspect today?

Developers can inspect the documented install contracts, MCP tools, CLI flow, and managed/open boundary while the public repository split remains a launch follow-up.

Why not open the whole engine?

The launch split keeps the install surface auditable while keeping the hosted memory service, tenant isolation, billing, and evaluation systems managed.

FIG. 5 - INSTALL

Inspect the edge before you connect memory.

Start with the MCP server package, then use the product and security pages to evaluate the managed layer behind it.

Open: MCP server and CLI
Managed: engine, index, billing, evals
Command: npx answer-engine-mcp
CLI: ae