Frequently asked questions

An all-in-one platform with three integrated products: Captia captures data at the first link (workshop, field, cooperative), Tracium anchors it on-chain with multi-actor traceability, Fidenta issues the QR-accessible Digital Product Passport. For any multi-actor value chain.

ERPs capture data inside your company. Darwin covers multi-actor from primary producer to end consumer, with blockchain integrity, multi-framework compliance (FSMA 204, EUDR, GS1 EPCIS and emerging frameworks) and AI over chain-wide events. Your ERP stays as internal source of truth; Darwin runs alongside, not on top.

For multi-actor compliance you need an immutable record that no single actor in the chain can later modify. A shared database requires everyone to trust whoever runs it. Blockchain removes that single point of trust: every actor anchors hashes + checkpoints. Sensitive data (specs, costs, photos) stays off-chain under your control.

Darwin delivers audit-ready records compatible with each framework. It is not the certifier. EUDR DDS is filed by the importer. FSMA 204 is filed by the obligated food operator. Private certifications (Rainforest Alliance, RSPO, FSC) are issued by each accredited body. Our role: records that hold up under audit. Yours: present them through your existing compliance workflow.

FSMA 204 (FDA, US, high-risk foods, effective 2028-07-20), EUDR (EU, deforestation-free, 7 commodities, effective Dec 2026), GS1 EPCIS 2.0 (global event standard) and emerging frameworks. The data model is agnostic: new frameworks add as mappings, not rebuilds.

Anyone manufacturing, processing, packing, or holding foods on the FDA Food Traceability List (FTL) with US destination or transit. Includes seafood, soft cheeses, leafy greens, fresh fruits, cut vegetables. The obligation runs throughout the supply chain.

The FDA can reject products at the border, recall them, or issue fines. Potential loss of US market access, reputational damage with retailers, operational impact on your export chain.

7 commodities and their derivatives entering the EU: cattle, cocoa, coffee, palm, rubber, soya, wood. Covers operators and traders importing or trading these products.

Without a Due Diligence Statement (DDS), the shipment cannot enter the EU market. Significant fines, possible product seizure, and blocking of repeat-offender operators.

It does not replace the EUDR DDS. Private certifications (Rainforest, RSPO, FSC) are complementary: they provide evidence, but the operator must still file the DDS with parcel-level geolocation and own due diligence. Darwin consolidates both into a single dossier.

Via managed API connectors. Your ERP stays as source of truth for your internal chain (receiving, production, dispatch). Captia connects so the first-link data (workshop, field, cooperative) that today arrives on paper lands structured in the ERP. Integration is defined in the Discovery phase.

No. Darwin sits alongside your systems, not on top. Captia fills the first-link gap; Tracium consolidates the multi-actor chain; your ERPs keep running. No rip-and-replace.

Yes. Captia has offline-first capture with automatic sync. Designed for rural operations with intermittent connectivity: the operator captures from a phone, data uploads when the network returns.

Parcel-level: parcels under 4 ha can use a single point, larger parcels need a polygon. Captia takes automatic GPS at capture, tied to the producer/lot. For larger parcels we can load KML/GeoJSON polygons from the cooperative or your ERP.

We cross captured coordinates with forest cover datasets (Hansen, Sentinel) to validate post-2020 no-deforestation. Satellite evidence is anchored on-chain alongside the DDS. The auditor can walk the full traceability: capture → satellite → DDS → import.

Yes. ERP connectors cover that case. Captia is optional for tier-1 if everything is already captured in system. Darwin shines when a tier-1 with ERP needs data from tier-2 that today arrives on paper or by email.

Because the lot is what your business measures: kilos harvested, containers exported, batches produced. A blockchain transaction is a technical abstraction you don't control (one lot can produce multiple transactions depending on process flow). Charging by lots aligns pricing with business value.

You only pay the difference at the plan's unit price, you don't escalate to another tier. No projections, no surprises: we bill on actual usage measured on the platform every month.

No. Blockchain infrastructure is managed by Darwin: nodes, gas, service wallets. You pay in fiat (USD, ARS, BRL, MXN by market). Gas, keys, and nodes are our problem.

No. Critical data is on-chain on a public blockchain (verifiable by any auditor without accessing Darwin). Your off-chain metadata is exportable any time via our APIs (event dumps, NFT exports, IPFS CIDs). No tech lock-in.

Yes. Upgrade or downgrade takes effect at the next billing cycle. No change penalties. The annual contract has a discount over monthly; early termination is handled case by case.

A one-time payment before Go-Live: Discovery (mapping your chain, identifying Critical Tracking Events) + MVP (a pilot with a subset of operations, ERP integrations, mobile forms, first on-chain record) + Go-Live (scale-up, training, dashboards). 4-8 weeks for pilot; 3-6 months for full go-live by scope.

End-to-end encryption, role-based access control, customer data sovereignty. Only what is strictly necessary goes on-chain (hashes, actor identity, custody checkpoints). Sensitive data (specs, costs, photos, PII) stays protected off-chain.

On-chain data stays permanently verifiable on the blockchain (we cannot delete it even if we wanted to). Off-chain metadata we export in standard format (JSON, EPCIS 2.0) for migration to another system. No lock-in.

No. Only hashes, custody checkpoints, and actor identity are anchored on-chain. All sensitive data (specs, drawings, process parameters, costs, recipes) stays off-chain under your control. Verifiability does not require exposing content. Like Git: the SHA proves integrity, the diff lives in your repo.

Personal data does NOT go on-chain (would violate GDPR right-to-be-forgotten). Operator, smallholder, and auditor identities are managed via cryptographic DIDs + redactable off-chain tables. The chain stores only hash references that contain no PII.

FSMA 204 (FDA), EUDR (EU), GS1 EPCIS 2.0, Global GAP, BRC, Rainforest Alliance, Fair Trade, and other private certifications. One dataset serves multiple standards: capture once in Captia, generate bundles in formats required by each destination.

Yes. Captia, Tracium, and Fidenta work together but also separately. You can start by capturing with Captia and add Tracium and Fidenta in later stages.

Captia is so simple it onboards in minutes, even for operators with little digital experience. We have adoption playbooks proven in rural operations. And for those without smartphones, the cooperative coordinator can load the data.

No. Anomaly detection runs on deterministic rules + configured thresholds over your live data. No training set needed. The agentic part uses LLMs over your chain events + current regulation; also not trained on your data.

Each alert arrives with: exact reason, referenced regulation section, the event that triggered it (with link to the on-chain tx), and suggested action. So your team knows what to do without reading code or models.

Yes. Each alert can be acknowledged / dismissed / escalated. The history stays auditable on-chain (including dismissals). Rules are tuned on confirmed false positives to reduce noise.

Real time for deterministic rules (cold-chain, ghost lots, custody gaps, cert expiry, timing): evaluated on every capture. Agentic queries are on-demand (user query).

Deterministic rules, yes (run in your infrastructure with no external calls). The agentic part (LLM) is optional and configurable: you can use our managed endpoint or your own on-premise model (OpenAI API compatible).

A BI shows aggregations; AI Insights detects and explains. Where your BI says "5% loss this month", AI Insights says "lot LOT-8901 lost 80kg between plant and dispatch, custody broken at 14:35, operator X". Actionable, not just informative.

Quickest path: a 2-week Discovery mapping your chain, identifying Critical Tracking Events, designing the pilot. Then a 4-8 week MVP with a subset of operations, then Go-Live to the rest. See /en/precios for tiers + estimates.

Yes. Dedicated sandbox with synthetic data, same APIs as production, no on-chain finality cost. Request it at tech@darwinevolution.io. You get credentials within one business day. More detail at docs.darwinevolution.io.

Typical pilot: 4 to 8 weeks. Full go-live (your entire operation): 3 to 6 months by scope and stakeholders. Mid-size operations are usually solidly in production in 4-5 months. More detail per vertical in By vertical.