What a cold-chain operating record needs
Explore the source, regime, calibration, context, ownership, and review details that make an alert useful to a team.
Read the cold-chain overviewResources
Useful questions for connected-asset operations.
These public explainers outline the operating ideas behind ciliot: turning signals into accountable action, retaining context, and evaluating a customer-specific pilot with disciplined claims.
Start where your team is
Read the operating question behind the product.
Each resource is an introduction, not a substitute for a customer-specific design, compliance review, or production acceptance evidence.
From connected signal to operational action
See how shared context, domain policy, human workflow, and reviewable records work together across a platform.
Read the platform approachPrepare for a grounded pilot conversation
Bring representative sites, operational scenarios, evidence needs, contacts, and a measurable hypothesis to the first discussion.
Prepare a pilot conversationA responsible claims checklist
Ask what evidence a statement needs before it becomes a promise.
A useful product conversation distinguishes capability from outcome. This helps teams avoid turning a test, a feature, or an in-range sensor value into a claim that exceeds its evidence.
- CapabilityIs the feature released, documented, and confirmed by its accountable product owner?
- PerformanceIs the methodology, environment, time period, and independently reviewable result clear?
- Commercial valueIs there a customer-specific baseline, formula, approval, and permission to publish?
- Security or complianceIs the scope, formal evidence, expiry, and legal/security approval current?
“A clear operating record is more valuable than a confident-looking dashboard with no context.”
Frequently asked questions
Clarify the boundary before you commit.
These answers set the scope of an initial conversation. Exact device, integration, security, data residency, and regulatory requirements are assessed with the customer.
Which sectors can use ciliot?
The platform is designed to support connected-asset operations in retail, food distribution and logistics, hospitality, healthcare and life sciences, industry, commercial real estate, agriculture, and transport. The first full service is cold chain; each new service needs its own defined scope and acceptance evidence.
Will ciliot work with every IoT device?
No universal compatibility claim is made. The platform uses replaceable adapters and reusable contracts. A project validates the specific devices, gateways, connectivity, and support boundaries that matter to the proposed service.
Can ciliot make a refrigeration decision on our behalf?
No. The initial product supports monitoring, evidence, and accountable human workflow. Controller writes require separate safety engineering, authorization, audit, and customer acceptance.
How is a pilot evaluated?
With a representative site population and operational scenario, planned drills, agreed data sources, a documented benefit baseline or hypothesis, named owners, and a review of both the evidence and limitations.
Keep the conversation specific
Bring your operational question, not a generic use case.
We will use the first discussion to understand the people, sites, assets, systems, evidence, and decision boundaries that matter to your team.