Turnstile v1.1

Turnstile v1.1

Governed model access, provider onboarding, image generation, and request accounting updates for existing and new Turnstile installations.

Highlights

• Databricks Workspace connections through the selected APIM managed identity, with native Anthropic Messages publication and streaming invocation.
• Governed image generation with permission and budget enforcement, image preview/download, redacted Request Trace, and versioned usage evidence.
• OpenAI-compatible provider onboarding, including Kimi, with isolated connections and model configuration.
• Application creation waits for authenticated data-plane readiness, not only an active management-plane subscription.
• People model-access changes immediately project the complete model ID/alias set to the APIM ledger, including replacement and explicit deny-all.
• Correlation-based request-attempt accounting, budget reservation reconciliation, model editing, and persistent table-column controls.

Deployment

• Upgrading v1.0: follow the upgrade guide. Preserve the original state, database, ledger, APIM, identities and historical usage. Apply pending migrations and required infrastructure changes as well as the application packages.
• Installing from zero: follow the clean-install guide. Use new deployment state and a unique resource prefix; a new StandardV2 APIM is the default. Provider resources and models must already exist separately.
• A private ledger requires API VNet connectivity and an App Service plan supporting regional VNet integration, B1 or higher. A ZIP update alone cannot supply missing network access, Table permissions or APIM operations.
• Image generation and the one-time evidence-v2 cutoff require separate opt-in. Databricks OAuth M2M remains disabled by default; installing the platform does not authorize its APIM identity in a provider Workspace.

Validation And Limits

• Both an existing-installation upgrade and a new clean Azure installation passed authenticated browser validation for Foundry text, PNG image generation, Kimi, Databricks managed identity, Application readiness, permissions, Trace, responsive UI, and model/Connection cleanup with retained history. Actual image and Kimi usage passed independent database settlement checks; temporary test settings were restored.
• The tested product candidate is a13085318e2bccfe090c623876d14d102efa504e. The final release adds documentation-only version metadata; runtime code, infrastructure, migrations and dependency locks remain identical to that candidate. The local gate passed 1,297 Python tests, type checks, frontend builds and contract/infrastructure checks.
• Actual image E2E covers the approved PNG path. Desktop interactive Entra sign-in, live multi-writer concurrency, multi-backend routing, Databricks OAuth M2M, cross-tenant flows and all provider failure branches are not established by these runs.
• When a model has no configured pricing, the Application view can display an estimated cost of $0.00. This is not evidence of free usage or a zero provider invoice; use token accounting and configure pricing before interpreting cost totals.