⚠ BETA TEST · evaluation only · no production use · please report bugs
Cellule-PRO · Public BETA

Try the BETA — 60 days free

The exact same Docker image that ships to paying customers — protected core, offline licence, GDPR self-service — with an evaluation licence that expires after 60 days. Help us improve the product by reporting bugs.

🎁 First 3 slots — Cellule-PRO pioneers

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.

⏳

2 years free

Not 60 days — 2 full years of free production use, priority support included. New JWT licenses re-issued each year.

💎

Lifetime pioneer pricing

After year 2, a permanent pioneer tariff well below standard Starter, degressive on additional pools:

Pool #1
€1,000 / year
Pool #2
€750 / year
Pool #3 and beyond
€500 / year

⚙ 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.

🤝

In exchange

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.

BETA terms — please read before installing

By pulling and running the BETA image, you accept these conditions:

  • Evaluation only. The BETA is provided for technical evaluation only. Not for production use. Don't feed it real client data unless that data is also evaluation/test material.
  • No warranty. The BETA is provided "as is", without any express or implied warranty. We make our best effort to ship a working build, but bugs are expected — that's why it's a BETA.
  • No liability. We accept no liability for data loss, service interruption, regulatory exposure, or any indirect damage resulting from BETA use. Run it on a machine you can wipe.
  • 60-day evaluation. On first start, the pool grants itself a 60-day evaluation. After that, nothing is deleted and your data stays readable; new actions wait until you paste a license (paid plan or BETA extension). Pioneer program excepted: the first 3 organizations receive standalone production licenses, re-issued yearly for 2 years — see the pioneer offer above.
  • Bug reporting expected. If you hit a bug, please email [email protected] with the version tag, the steps to reproduce, and (if possible) the relevant pool log excerpt.
  • Confidentiality. The image contains compiled components. Reverse-engineering and decompilation are prohibited. You may pass the unmodified BETA image to a colleague for evaluation; any other redistribution, modification or resale is prohibited.
  • Termination. We may revoke any BETA license at any time, no reason required. Your data stays yours on your hardware; we don't have remote kill of your data.
How you accept: there is no click-through. Pulling the image after reading this page is your acceptance. If you don't agree with the terms above, please don't pull.

How to install the BETA

Three steps. The first-boot wizard handles setup in a few minutes.

Cellule-PRO has three parts:

  • Pool (this install) — the heart of the system: one Docker server on your network, no graphics card needed. It serves the chat, documents, admin dashboard, API and model distribution.
  • Workers — the machines that run the AI models: office PCs, workstations or dedicated servers, Windows or Linux. They install in one command and fetch everything from your pool, never from the Internet.
  • Proxies (optional) — connect an AI engine already running on one of your machines.

Install the pool first. Pool requirements: Ubuntu 22.04+ / Debian 12+, Docker 24+, 16–32 GB RAM, 200 GB disk. For the machines running the models, see “What hardware do we need?” on the home page.

1

Install — no license needed to start

Download the image anonymously (below) and start it: the pool grants itself a 60-day evaluation on first start. You can still email [email protected] beforehand with your company name, evaluation scope and number of pools (sites): we'll help you size the hardware.

2

Get the image + start

The BETA image is about 7 GB compressed. The database (PostgreSQL + pgvector) is included in the compose file, and the text-understanding model is already inside the image: nothing to download at runtime.

Docker registry pull (anonymous)

Resumable, and faster on updates (only changed layers are downloaded). No docker login needed — read access is open. The image is distributed freely; the license, bound to your own pools, is what keeps it in production.

# Anonymous pull from our self-hosted registry:
docker pull registry.pro.cellule.ai/cellule-pro-beta:latest

Then start the stack

# Put the compose file next to a .env containing POSTGRES_PASSWORD=<your choice>,
# then start (no license needed: 60-day evaluation on first start):
docker compose -f docker-compose-beta.yml up -d

# Compose template:
#   https://pro.cellule.ai/docker-compose-beta.yml
3

First-boot wizard

Open https://<your-server>:18443/setup/ui (or http://<your-server>:18095/setup/ui). The first time, your browser warns about the pool's own certificate: compare its fingerprint with the one shown in the dashboard, “HTTPS” tab. The wizard then guides you through: admin account, cluster name, sector preset, employee sign-up policy, logo. About 5 minutes.

🔑 Getting your license. Dashboard → License → « Download licence request »: download the .json file and email it to [email protected]. You receive a license signed for your pools only (it cannot be reused elsewhere): paste it on the same page — no restart. Same steps for a renewal.
The complete installation and the installation profile, in 3 minutes — real screens: Docker image, first-boot wizard, the four installation profiles (none preselected), settings already ticked by the profile, a pool with another profile refused, and Supervision.
Stuck during install? Email [email protected] with your environment description. Free remote assist included in the BETA — we want you to succeed and to harvest your feedback.

Documentation — fully embedded, bilingual

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.

📘

ADMIN_GUIDE

Step-by-step operations manual for your IT team: installation, wizard, daily operations, backup, multi-site federation, licence. Covers everything clickable in the admin dashboard.

🔌

API_REFERENCE

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.

🔒

SECURITY_MODEL

Security model: trust boundaries, signed exchanges between sites, offline licence, GDPR anonymisation, append-only audit. The document your CISO will ask for.

🧠

USER_GUIDE

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.

🏛️

CELLULE_PRO_ARCHITECTURE

Architecture overview: the four layers (worker, pool, federation, governance), how your sites work together, how models reach your machines.

🛠️

TOOLS_MODE

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.

Once installed: open the admin dashboard, “Docs” tab, choose a document and a language, and print it to PDF if you need to share it. The documentation always matches the version you run.

Before installing? The complete documentation (admin guide, API reference, security model, architecture) is provided with the image and on request at [email protected] — see the documentation page.

Report a bug

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.

BETA — frequently asked questions

Is the BETA functionally complete?

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.

What happens after the 60 days?

Nothing is deleted and nothing stops at startup: your conversations, documents and settings stay readable. New actions wait until you paste a license — a paid plan, or a BETA extension if you want to keep testing. If you're one of the 3 pioneer organizations, this doesn't apply — you get 2 years of free production licenses instead.

Can I extend the 60 days?

Yes, in good faith. If your evaluation is going well and you need more time, send us a license request from the License page with a word on the current status: we'll issue an extension. The 60 days are a default, not a hard rule against engaged evaluators.

Do you collect telemetry from the BETA image?

No. The BETA image is closed by default — 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.

Can I share the BETA image with a colleague?

Yes: the image itself is freely distributed (anonymous registry pull or tarball). Each installed pool starts its own 60-day evaluation. The license, on the other hand, is signed for the pools listed in your request: it only works on those pools — that's how real usage is tracked and how per-pool pricing stays consistent. To evaluate several sites, send one request covering all of them.

What if I find a serious security bug?

Email [email protected] with subject "security bug" — we'll respond within 72 business hours at most, ship a fix, and credit you in the changelog (with your consent). Coordinated disclosure preferred over public disclosure.