Security & trust
Trust is a design decision.
We do not display security badges here; they are easy to add and hard to verify. Instead, this page describes what the software actually does — how evidence is labelled, how outputs stay traceable, and how you can run everything yourself — followed by the plain facts about what celaron.com does with your visit.
RESPONSIBLE DISCLOSURE WELCOME
Evidence policy
Every number says where it came from.
Raw experimental or instrument result.
Output of a real engine run — PyBaMM, M3GNet, pycalphad.
Registered model output with calibrated uncertainty.
Pulled from literature, flagged for review.
A generative proposal, never presented as fact.
Synthetic or illustrative — never billed, never disguised.
Every product number also carries an engine card naming the engine, version, license, and limitations behind it. This website follows the same rule: its claims link to live sources — public benchmark pages, live API counts, and published research. If we cannot verify a claim, we do not publish it.
Provenance and audit
Outputs that show their work.
- Result outputs link back to the source run that produced them.
- Every number carries an engine card naming the engine, version, license, and limitations behind it.
- Reproducibility bundles ship with results, so a dossier can survive publication review.
- Matflow states that its audit logs are tamper-evident, so the record can be checked rather than merely trusted.
The provenance and audit statements above describe what the Matflow product documents about itself. We are not adding guarantees beyond the product’s own documentation.
Self-hosting and data ownership
Your data does not have to leave your building.
Matflow
Run it yourself, export what you make.
Matflow supports Docker self-hosting, ONNX and joblib model export, and dataset export. Deploy it on your private cloud or on-premise hardware, and take your models and data with you whenever you choose.
Celaron Chat
An open stack, not a black box.
Celaron Chat runs on the open-source Open WebUI stack, and the same stack can be deployed in your environment. You can inspect what runs, extend it, or host it where your conversations already live.
Open stacks and exportable formats mean no vendor lock-in. Leaving is always possible — which is why staying is a choice.
This website
The plain facts about celaron.com.
- celaron.com is statically exported and served from our own infrastructure — there is no application server between you and these pages.
- It sets no cookies and runs no analytics. Nothing on this site profiles you.
- It loads no third-party scripts and sends no data to advertising or tracking networks.
- The only data we collect is the email you choose to send us.
- Pages are served over HTTPS with a certificate from Let’s Encrypt.
- Links out to Matflow, CAPRI, and Celaron Chat leave this site; those platforms are governed by their own policies.
You do not have to take our word for it: open your browser’s network inspector on any page here and you will see requests for this site’s own files and nothing else. The privacy notice covers server logs and email in more detail.
Report a vulnerability
Tell us before you tell the world.
Email support@celaron.com or bassil@celaron.com with enough detail to reproduce the issue and give us a reasonable window to fix it before you disclose publicly. We will acknowledge your report and keep you updated as we investigate. We will not pursue good-faith researchers who avoid privacy violations, data destruction, and disruption of our services.
Questions about our security posture?
Ask us directly. Whether you are a researcher, a security reviewer, or a team weighing self-hosting, a human answers.