The exact same hardened Docker image that ships to paying customers — compiled IP-critical modules, multi-key signing, GDPR articles 15-22 native — with a time-limited license that expires after 60 days. Help us harden the product by reporting bugs.
The first 3 organizations that engage seriously with the BETA and go to production with Cellule-PRO get a pioneer status with the extended privileges below — well beyond the standard 60-day free evaluation.
Not 60 days — 2 full years of free production use, priority support included. New JWT licenses re-issued each year.
After year 2, a permanent pioneer tariff well below standard Starter, degressive on additional pools:
⚙ One signed JWT per pool. Each additional site = an additional license to request (issued on demand, no extra cost during the 2-year free window). Same client_id, distinct keys — that's how the per-pool model stays auditable.
Right to display your logo + one public citation (1-sentence quote) on landing and pricing pages. Optional: 1-page case study we draft, you review.
How to apply: email
[email protected]
with subject Pioneer application. Include: company name, sector,
intended use case, target deployment date. We select on intent and fit, not
first-come-first-served.
Once the 3 slots are filled, this offer closes — followers go to standard Starter pricing.
By pulling and running the BETA image, you accept these conditions:
cellule.ai) under AGPLv3 is the legal channel for source code access.Three steps. The first-boot wizard handles setup in 5 minutes — a DSI/sysadmin deploys without reading the docs first.
Cellule-PRO is a distributed sovereign microsystem built around 3 components:
For the BETA, install the pool first. Requirements: Ubuntu 22.04+ / Debian 12+, Docker 24+, 16-32 GB RAM, 200 GB disk. GPU optional on the pool: if you have one (RTX 4060+ / A4000+), the pool runs inference itself for ≤ 9B models in early testing — but the design intent is to deploy workers on employee desktops to handle production load. Workers install in one command, hardware auto-detected by the pool.
Email [email protected] with: company name, intended evaluation scope (employees / data / use cases), target hardware, and the number of pools (sites) you plan to deploy. You'll receive within 24h business hours your 60-day Ed25519-signed JWT license(s) as file attachment(s) — one signed JWT per pool — plus the docker-compose.yml template. The image itself (Options A and B below) is downloadable anonymously — the license is what unlocks each pool.
The hardened BETA image is ~5.2 GB compressed. Pick whichever option fits your setup. Both ship the same content: signed Cython-compiled binaries, PostgreSQL+pgvector sidecar in the compose, multilingual MiniLM embedder pre-downloaded inside.
Option A — Direct download (recommended for first install)
One file, one download, no login. Resume-able with curl -C -. The image is useless without the signed JWT license you received by email — that's the actual access control.
📥 cellule-pro-beta-latest.tar.gz (5.2 GB)
# Anonymous resume-able download:
curl -C - -O https://pro.cellule.ai/download/cellule-pro-beta-latest.tar.gz
# Verify integrity (checksums published next to the file):
curl -O https://pro.cellule.ai/download/cellule-pro-beta-latest.tar.gz.md5
curl -O https://pro.cellule.ai/download/cellule-pro-beta-latest.tar.gz.sha256
md5sum -c cellule-pro-beta-latest.tar.gz.md5
sha256sum -c cellule-pro-beta-latest.tar.gz.sha256
# Load into Docker:
docker load -i cellule-pro-beta-latest.tar.gzOption B — Docker registry pull (anonymous)
If you already use a Docker registry workflow. Slightly faster on re-deploys (layer cache). No docker login needed — read access is open.
# Anonymous pull from our self-hosted registry:
docker pull registry.pro.cellule.ai/cellule-pro-beta:latestThen start the stack (both options)
# Drop the .env (with your JWT license) next to the compose.yml we sent you,
# then start:
docker compose -f docker-compose-beta.yml up -d
# Compose template also downloadable:
# https://pro.cellule.ai/docker-compose-beta.ymlOpen http://<your-server>:18095/setup in a browser. The wizard guides you through: admin account creation, cluster name, sector preset (legal / health / industrial / defense), employee signup policy, branding (logo upload). Takes 5 minutes. After that, you're chatting.
CELLULE_LICENSE_PATH in your .env), the container refuses to start and logs license missing/invalid. This is deliberate — the open image distribution is paired with cryptographic license control so the BETA stays evaluation-only. Email [email protected] first to receive your 60-day JWT.
The complete reference documentation ships inside the Docker image and is served by the admin dashboard once installed — no separate doc site to keep in sync, no external CDN, no phone-home. Available in English and French, printable to PDF in one click from the dashboard.
Step-by-step operations manual for your DSI: install, wizard, daily ops, backup, multi-site federation, ceremony procedure. ~80 sections covering everything that's clickable in the admin dashboard.
Full OpenAI-compatible endpoint reference for sk-cellule-* token usage with opencode, Continue.dev, Cursor, OpenWebUI, or your own Python openai SDK code. Includes /v1/chat/completions, /v1/embeddings, /v1/models.
Trust boundaries explained: LAN-trust between workers and pool, Ed25519 federation signing, JWT EdDSA license validator, GDPR-cascade anonymization, audit trail append-only. The doc your CISO will ask for.
Employee-facing guide: login, chat, document RAG (drag-drop), [MEMORIZE: fact] mode, debate mode, project mode, GDPR self-service portal. Suitable to email to your pilot employees on day 1.
Technical architecture deep-dive: four-layer model (atom / pool / federation / governance), Ed25519 federation flow, MoE sharding, smart routing logic, model catalog replication.
Function-calling and tool-use reference for integrating Cellule-PRO into agentic workflows. Compatible with the OpenAI tool-use schema used by Claude, GPT-4, Mistral function-calling.
http://<your-server>:18095/v1/admin/dashboard/ui, click the
"Docs" tab, pick a doc, switch language EN/FR at the top right, print to PDF
if you need to share with management. Same documentation, same content, same
version as the running image — no drift possible.
For the BETA period we collect feedback by email. A persistent in-app feedback form (with database backing) is on the roadmap — for now, plain email beats under-tested form code.
Include: the image version tag (visible in the admin dashboard under "About"), the steps to reproduce, what you expected, what happened, and any relevant docker logs cellule-pool excerpt around the issue. Screenshots welcome.
Yes. It's the exact same image that ships to paying customers — chat, RAG, project mode, OpenAI-compatible API, GDPR self-service, admin dashboard, multi-site federation. Only the license is time-limited. There's no "feature crippling" between BETA and paid.
The pool refuses to start a new container until you provide a new license. The data on your PostgreSQL and the model files on disk are not deleted — you can resume operation by buying a paid plan and getting a fresh JWT, or by requesting a new BETA build if you want to keep testing.
Yes, in good faith. If your evaluation is going well and you need more time, email us with the current status and we'll issue an extension JWT. The 60 days are a default, not a hard rule against engaged evaluators.
No. The BETA image is air-gap by design — no phone-home, no analytics, no remote telemetry. Bug reports happen via email, sent by you when you decide to. Same posture as the paid plans: your data stays home.
Within your organization, sharing the JWT among colleagues evaluating the same pool is fine — the license is bound to your client_id and to that one installed pool. To evaluate several sites in parallel, or for a colleague starting their own evaluation, please request an additional JWT (one per pool, one per evaluator). The image itself is open-distributable (anonymous tarball or registry pull) — it's the signed JWT that's nominative, that's how we track real usage and how the per-pool pricing model stays consistent.
Email [email protected] with subject "security bug" — we'll respond within 24h business hours, ship a fix, and credit you in the changelog (with your consent). Coordinated disclosure preferred over public disclosure.