pliqra/
2.1.0Stable community release

Your models.
Your rules.
One clear contract.

Turn a deployed model endpoint into a governed AI service. Connect applications, shape access and limits, and make model changes explicit.

Explore the demoInstall Pliqra

Self-hosted·Apache-2.0·One Docker image to start

YOUR ENDPOINTS → YOUR AI SERVICESPolicy active
OpenAI-compatibleOllama / native APIs
pliqraRoute. Govern. Explain.
GuardrailsScoped accessUsage & cost
support-chatBound

chat · streaming · tools

Contract fingerprintfp_a91c
Applications know what they agreed to.
POST /v1/chat/completions200
FROM ENDPOINT TO APPLICATION
ConnectConfigureBindUnderstand every call

THE NEED

01 / CONTEXT

Give the changing parts
a dependable agreement.

A working endpoint is a starting point. Teams also need clear access rules, predictable limits and visibility into what happens when models or policies change.

01

Models keep changing.

Capabilities, deployments and policies evolve. Applications need to know when their accepted expectations no longer hold.

02

Governance gets scattered.

Teams, keys, quotas and guardrails need a shared place to configure, apply and inspect them.

03

Every call needs a trace.

A response should come with an explanation: selected model, attempts, checks, usage and estimated cost.

THE PLIQRA APPROACH

Make the agreement
part of the connection.

Applications can bind to a fingerprint of the service’s capabilities and gateway policy. A changed contract returns HTTP 409, so the application can deliberately rediscover and renew.

  • Declared capabilities and verified behavior stay separate.
  • Routing and policy decisions remain inspectable.
  • The same service can be governed through the UI or API.
Explore the connection protocol

Protocol 0.1 is a draft. Binding is opt-in; standard supported inference APIs are also available.

application → support-chat

01discoverchat, streaming, tools

02bindfingerprint: fp_a91c

Model or policy contract changes

03invoke409 ContractChanged

04renewExplicit application decision

New agreement accepted. Continue.
Illustrative protocol exchange · try it below

TAKE THE CONTROLS

02 / INTERACTIVE DEMO

Meet the whole
operating layer.

Eight short scenarios. Change a contract, exhaust a quota, inspect a guardrail, drain a site or review a fleet policy. No account or running model needed.

pliqra / product walkthroughInteractive simulation
Pliqra2.1

One workspace.
UI and API controls.

01 / 08

Give your application a clear agreement.

Discover a model, separate declared capabilities from verified behavior, and bind an application. Try changing the accepted contract.

01 / CONNECT ENDPOINT
https://model.example.test/v1
support-modelDiscovered
chat streaming tools

Declared inventory and verified checks are tracked separately in Pliqra.

02 / ACCEPT A CONTRACT
fp_a91cCapabilities + policy fingerprint
Bind → change the contract → invoke. See the boundary in action.
Implementation guide
Browser-only simulation. No model calls, account creation or credentials. Actual console screenshots use synthetic data.

THE CAPABILITY MAP

03 / PRODUCT

A catalog, a gateway
and the controls around it.

Configure in the console. Automate through the API. Start with an endpoint and add the operational capabilities your workload needs.

01

Serve the interfaces your apps use

Chat, embeddings, speech and transcription, Responses, Anthropic Messages and Ollama. Live native text/tool streams, within documented API subsets.

Read the guide
02

Build your own gateways

Service selection, project/team grants, request and token windows, budgets, concurrency, input/output bounds and scoped application keys.

Read the guide
03

Compose your guardrails

Local PII, keyword and schema checks. NeMo check APIs and custom HTTP validators. Ordered input/output stages, enforce/observe modes and visible verdicts.

Read the guide
04

Bring identity and secrets

OIDC, SAML, SCIM, workload JWT federation and project/team permissions. Environment, mounted-file and Vault secret references.

Read the guide
05

Explain usage and estimated cost

Cumulative administrator reporting, team and site filters, per-attempt routing, token accounting, unknown-usage handling and exports.

Read the guide
06

Publish with fresh evidence

Immutable prompt versions, durable batches, external judges, evaluations, quality gates and controlled canary traffic.

Read the guide
07

Operate across active sites

One writable PostgreSQL authority, strict shared admission, local-first placement, site drain, per-site health and safe fenced-process recovery.

Read the guide
08

Govern independent installations

Explicit pairing, combined metadata visibility, resource mapping, second-administrator approval, rollout receipts and policy drift.

Read the guide
09

Connect through explicit contracts

Discovery, capability/extension negotiation, fingerprinted bindings and deliberate renewal. Python, JavaScript/TypeScript and Go clients; draft protocol and executable core profile.

Read the guide
10

Keep operations recoverable

Encrypted backups, recovery tools, monitoring, audit trails and retention controls. SQLite by default; PostgreSQL, organizations and analytics when needed.

Read the guide

YOUR INFRASTRUCTURE

04 / TOPOLOGY

One image to begin.
Room for what comes next.

Pliqra runs alongside your already deployed models. A single installation starts with SQLite; shared deployments add PostgreSQL and your existing infrastructure.

Your appsSDKs or supported APIs
→
PliqraGateway + console + SQLite
→
Your model endpointsAlready deployed

Persist the data volume and encryption key. One SQLite process owns each volume. Configure HTTPS before exposing a workspace remotely.

Deployment details

SHIPPED WITH EVIDENCE

A stable release.
Checks you can inspect.

9,000/9,000

Successful synthetic soak calls

30 min

Continuous synthetic acceptance

113 ms

Observed synthetic p95 latency

2.1.0 acceptance · 7 November 2026. One host, 4 CPUs, PostgreSQL 18 and a deterministic 5 ms model fixture. Native AMD64/ARM64 smoke, model/database interruption recovery and RC4 SQLite upgrade/backup recovery also passed. Bounded regression evidence, not production sizing or an availability SLA.

Inspect the evidence

MAKE YOUR FIRST CONNECTION

Bring an endpoint.
Start here.

Use the ready-made Linux AMD64/ARM64 image. Docker Desktop runs the matching Linux image on macOS or Windows. No source build or registry login required.

  1. 1
    Start Pliqra.

    Docker with Compose is required. Run the commands, then open localhost:8088.

  2. 2
    Connect your model.

    Create the administrator and add a reachable endpoint. Host-based models use host.docker.internal.

  3. 3
    Publish and connect.

    Configure the service and gateway, create a scoped key, then connect your application.

Complete first-call guide
TERMINAL / PLIQRA 2.1.0
mkdir pliqra && cd pliqra
curl -fL -o compose.release.yaml https://github.com/eturkok/pliqra/releases/download/v2.1.0/compose.release.yaml
docker compose -f compose.release.yaml pull
docker compose -f compose.release.yaml up -d
Loopback by default. Persist the volume; configure HTTPS for remote access.
Image digests, checksums and upgrade guide

A FEW CLEAR ANSWERS

Know the boundaries.
Keep the control.

Does Pliqra deploy or train models?
Pliqra connects to already running model endpoints. You manage GPU capacity, model serving and training; Pliqra governs access, routing, contracts and usage.
What changes when an application binds to a contract?
A bound application accepts a fingerprint of its service capabilities and applicable gateway policy. A changed contract returns HTTP 409 and the application explicitly renews. Supported inference APIs are also available without protocol binding.
Does the demo make real model calls?
No. Scenarios run entirely in your browser with illustrative values. Console images are actual screenshots from synthetic workspaces. No account or credential is needed.
How do multi-DC quotas stay strict?
Active gateways use one shared writable PostgreSQL authority. A site that cannot reach it stops new admission. Your deployment supplies database HA, durable promotion and ingress. Read the consistency and recovery boundaries.
Can I bring my identity provider and guardrails?
Pliqra implements documented OIDC, SAML and SCIM behavior and calls configured NeMo check APIs or custom HTTP validators. Actual vendor tenants and guardrail deployments require environment-specific acceptance. See the compatibility matrix.
Is Pliqra free for commercial use?
Pliqra is licensed under Apache-2.0, allowing commercial use, modification and redistribution under its terms. Community support is best-effort. Read the license and support envelope.

MODELS WILL CHANGE. KEEP THE AGREEMENT VISIBLE.

Connect with confidence.
Keep your rules in reach.

Get started with Pliqra Explore the source