Changelog

What's new in Algenta — notable releases, improvements, and fixes to the engine, SDKs, MCP server, and self-hosted deployment, newest first.

What's new in Algenta — the engine and the four ways to reach it (HTTP API, SDKs, MCP, self-hosted deployment), newest first. Each entry is dated and tagged; follow the links for the full detail.

We call out behavior changes with a Changed tag — pin your SDK version and read these before upgrading.

Account and sign-in endpoints live only under /v1

Changed

• Sign-in (/v1/auth/*), device login (/v1/oauth/device/*), the account portal (/v1/account/*), the public price list (/v1/billing/plans) and website provider keys (/v1/byok) are served only under /v1. The same paths without the /v1 prefix no longer answer. See API stability.

• The website's separate usage read is removed.

• The MCP server speaks Streamable HTTP at /mcp only. The older HTTP+SSE transport and the platform contract's mcp_legacy_sse_endpoint field are removed.

Fixed

• POST /v1/auth/signup creates the account instead of failing with a server error.

• Verification and password-reset emails link to the engine's own /v1/auth/* endpoints on its public API URL.

Reworked documentation and a single licensing model

A full documentation refresh on a shared, audited docs system — plus a simpler licensing model.

New

• A live, interactive API explorer — set your key and base URL, then call every endpoint from the browser.

• A friendlier, help-center-style Troubleshooting page: a quick-fix table plus expandable cards by symptom.

• A Connectors section — overview, full reference, and per-source guides (Snowflake, BigQuery, ClickHouse, REST).

• Agentic and long-running guides: run an agent, async jobs, and repository intelligence.

• Deploy-and-integrate guides: BYOK, device binding, air-gapped, and CI/CD.

• Testing with Algenta and deeper SDK coverage, plus operate guides for monitoring and encryption at rest.

• Using these docs with AI — the llms.txt context files, per-page Markdown, and the docs MCP server.

Improved

• A cleaner landing page and consistent navigation across every page.

Changed

• Licensing now uses a single v2 format — install the v2 license file Algenta provides. The legacy v1 format was retired. See Licensing.

Self-hosted install, privacy proof, and end-to-end checks

Everything needed to run Algenta on your own infrastructure — and to prove it stays private.

New

• One-command self-hosted install (Docker Compose: api + worker + Postgres + Redis + object storage).

• A privacy report (GET /v1/admin/privacy-report) that proves a deployment is cloud-free, with a 24-hour egress summary.

• Smoke and persistence proof scripts that exercise the full stack end to end (self_host_smoke.sh, self_host_persistence_proof.sh).

• The strict air-gapped profile (ALGENTA_DEPLOYMENT_MODE=air_gapped) and a telemetry-disable switch.

The engine, four surfaces, and offline licensing

The Algenta engine and every surface that reaches it.

New

• The HTTP API under /v1 — Monte Carlo simulation, decisions, governed data, and async jobs.

• Python SDK (algenta-sdk, AlgentaClient), TypeScript SDK (algenta-sdk, AlgentaClient), and the in-process algenta runtime surface that is rolling toward public registry release.

• The MCP server (algenta-mcp) — governed datasets, exact queries, simulations, and agent runs exposed as tools for Cursor, Claude Desktop, and more.

• Durable, fully offline RS256 licensing with product entitlements and capacity caps, plus BYOK provider keys.

Keep going

InstallAPI explorer (live)