Talk to CalBrix
Speak directly with the engineer behind the platform.
CalBrix is a founder-led, early-access software project. Contact the founder to discuss demonstrated workflows, open limitations and the feasibility of your requirements.
Your point of contact
Philip Jojo Montford
Founder & Principal Engineer · CalBrix OS
The core workflow has been demonstrated with synthetic records. Production customer deployments and customer references have not been substantiated for this website; we are seeking evaluators, not presenting a record of established adoption.
Tell us about your laboratory or industrial workflow, its constraints and the controls you need. Regulatory suitability, integrations and deployment feasibility require assessment; no certification or compliance outcome is promised.
Use synthetic data for evaluation. Do not assume account registration establishes readiness for real calibration records.
Direct channel
Response times depend on availability and are not guaranteed. Do not send passwords, credentials or confidential calibration records by email.
Follow for product updates, calibration field notes, and release highlights. The founder also posts directly at in/philip-montford.
What to write about
Any question. No gatekeeping.
The same inbox handles technical questions, procurement, compliance mapping, integrations, and escalations.
Technical questions
Platform behaviour, calibration workflows, certificate output, MSA/SPC, uncertainty calculations, integrations.
Compliance & audit
Discuss the evidence and validation gaps relevant to your standards and intended use.
Multi-site rollout
Planning migrations from spreadsheets or legacy systems across multiple facilities and entities.
Single-tenant / on-prem
Assess private or on-premise requirements. Air-gapped operation and specific data-residency arrangements are not validated.
Procurement & contracts
Master Services Agreements, Data Processing Agreements, vendor security questionnaires, invoicing.
Feedback & feature requests
Share feedback with the founder. Feature requests do not imply a delivery commitment.
Start with the evidence.
Review the tested workflow and known limitations, then discuss an evaluation using synthetic data. Operational use requires a suitable deployment, resolved gaps and acceptance checks.