Pricing

Priced per line. Justified per batch.

One avoided rejected batch on a high-value product can pay for months of the Line tier. We would rather you started with one line and one number than with a plant-wide programme and a business case nobody believes.

From $17,000 / line / mo15 to 20% annual prepay discountOutcome components available

run_b2c7e1 · agent graph · scenario 10 nodes · 1 QA approval gate
01 · orchestrator ingest.batch_record ✓ SUCCEEDED 02 · orchestrator twin.rehearse ✓ SUCCEEDED 03 · blend_dispense blend.uniformity ✓ SUCCEEDED 04 · granulate_dry granulate.dry ✓ SUCCEEDED 05 · compress_fill compress.press ✓ SUCCEEDED 06 · coat_dry coat.spray ✓ SUCCEEDED 07 · defect_inspect inspect.tablets ✓ SUCCEEDED 08 · quality_potency spectra.release_evidence ✓ SUCCEEDED 09 · orchestrator approve.qa ◆ APPROVAL 10 · quality_conf release.genealogy ✓ SUCCEEDED

Scenario: Run one immediate-release tablet batch through granulation, compression, coating and inspection inside the approved design space, with QA approval before release. A design walkthrough, not a customer record.

Pricing

Priced per line, per plant, per group

Land on one validated workflow with a measurable baseline. Expand by line, module, site and autonomy level. Outcome components are available on yield, rejects, deviations and energy.

Billing period
Line $17,000 per compression, coating or granulation line / month · billed monthly

Compression or coating control or inspection AI for one line. For OSD makers validating ROI on the wedge.

  • One line, one agent module
  • Validated plant-edge inference node
  • Equipment, PAT and MES read; bounded write inside the design space
  • Run log, Part 11 audit trail, batch genealogy
  • Business-hours support
Start a validated pilot
Enterprise Custom land $750k to $10M ACV

Pharma and CDMO groups standardising on Pildeon across sites, with custom formulation, tooling and tolerance models.

  • Multi-site validated plant-edge fleet
  • Custom formulation, tooling and tolerance models
  • Validated on-prem deployment, air-gapped option
  • Group autonomy policy and approval chains
  • SLAs, SSO and RBAC, dedicated engineer
Contact us

Annual prepay discounts run 15 to 20% depending on term; the toggle shows 15%. Usage metering applies above plan limits. Multi-year enterprise agreements carry usage ramps.

Compare

What is in each plan

Modules are licensed per line on the Line tier and bundled on Plant and Enterprise.

What is in each plan
CapabilityLinePlantEnterprise
Lines covered1All on siteAll in group
Agent modules1 of 9All 9All 9 + custom
Twindra batch twin·IncludedCustom formulation and tooling models
Spectryn, Visqa, Conforma, KinetosOne module (Spectryn or Visqa or control)All includedAll included
Plant-edge nodeIncludedPer lineFleet managed
Bounded equipment writesScoped setpointsAll scoped setpointsGroup policy
Part 11 audit trail and genealogyIncludedIncludedIncluded + export API
Autonomy levelsL0 to L2L0 to L3L0 to L3, group policy
SSO, RBAC·SSOSSO + RBAC to the setpoint
Validated on-prem, air-gapped·OptionalIncluded
Validation artefactsModel cardsModel cards + change-control recordsFull site validation package
SupportBusiness hours24/724/7 + named engineer
Model reviewAnnualQuarterlyQuarterly per site
Indicative price$17,000/mo$100,000/mo$750k to $10M ACV
Outcome pricing

Pay a share of the number you moved

For the highest-value workflows, enterprise agreements can include an outcome component: a share of measured yield, reject, deviation, energy or first-pass-quality improvement against the shadow-mode baseline. The baseline method is agreed in writing first.

Usage

Metering above plan

Per batch, per line or per action above plan limits, so a growing campaign does not need a new contract.

Outcome

Share of measured improvement

Only against a baseline both sides signed, only on numbers reproducible from the plant's own records.

Guardrails

Floor pricing protected

Discounts are traded for term length and case-study rights, never for a weaker baseline method.

Run timeline · scenario

What you are actually buying

A run engine that produces this record on every batch, every shift, on every line you license.

run_b2c7e1 Line 2 · rotary tablet press · scenario SUCCEEDED
  1. 01 ingest.batch_record SUCCEEDED 1.2 s

    Plant Orchestrator · Pulled the master batch record, the approved design-space limits for this formulation and tooling family, and the site autonomy policy from MES; locked the target envelope for the run.

  2. 02 twin.rehearse SUCCEEDED 41 s

    Plant Orchestrator · Twindra simulated 36 candidate setpoint vectors on the as-made batch twin (granulation DEM, compression and ejection risk, coating CFD, dissolution surrogate) and ranked them on predicted content uniformity, capping risk and takt.

  3. 03 blend.uniformity SUCCEEDED 6 m 10 s

    Blend-and-Dispense · Spectryn scored in-line NIR spectra against the formulation's chemometric model; the blend reached its uniformity end point with confidence bounds inside the site acceptance limit and blending stopped on evidence rather than on a fixed time.

  4. 04 granulate.dry SUCCEEDED 3 m 48 s

    Granulate-and-Dry · Inlet air temperature and drying airflow trimmed inside the approved window to bring loss-on-drying to the target moisture band for compression; the move was bounded, logged and inside the design space.

  5. 05 compress.press SUCCEEDED 2 m 02 s

    Compress-and-Fill · Main compression force and feed-frame speed adjusted inside the approved window to hold tablet weight and hardness on target while the twin's capping-risk estimate stayed under the site threshold.

  6. 06 coat.spray SUCCEEDED 4 m 25 s

    Coat-and-Dry · Spray rate and inlet temperature re-phased against bed temperature and exhaust humidity to hold the film-coat window and avoid twinning and mottling; no excursion from the validated recipe envelope.

  7. 07 inspect.tablets SUCCEEDED continuous

    Defect-and-Inspect · Visqa classified chips, cracks, capping, spots, mottling and print defects on six synchronised cameras, within the sub-100 ms design budget, and linked a rising chip rate to coating spray rather than to tooling.

  8. 08 spectra.release_evidence SUCCEEDED 38 s

    Quality-and-Potency · Spectryn assembled the method-linked evidence chain for content uniformity and moisture with confidence bounds and citations to the validated analytical method, ready for QA review.

  9. 09 approve.qa APPROVAL 3 m 14 s

    Plant Orchestrator · Batch release is above every autonomy level Pildeon offers. The package was held for the named QA reviewer, who approved it in the review console; the decision, the reviewer identity and the timestamp are in the Part 11 audit trail.

  10. 10 release.genealogy SUCCEEDED 52 s

    Quality-and-Conformance · Conforma wrote the time-aligned batch genealogy (every sensor state, recommendation, approved action, equipment response and QC result) and the cited release package to the immutable audit trail.

Tool calls · scenario

The agent shows its work

Every tool invocation, argument and result is written to an immutable, human-readable log, and every reasoning step is expandable. Nothing about a run is hidden from the plant or from QA.

tool-call stream · run_b2c7e1
  1. 06:12:04mes.read_batch_record({ line: "L2", product: "IR tablet · family A" })
  2. 06:12:05ok design space loaded · autonomy policy L2 · QA reviewer assigned
  3. 06:12:06twin.simulate({ candidates: 36, horizon: "full batch" })
  4. 06:12:47ok candidate #14 selected · predicted CU inside limit · capping risk under threshold
  5. 06:12:48policy.evaluate({ candidate: 14, autonomy: "L2" })
  6. 06:12:48ok 5 setpoint moves inside design space · release held for QA
  7. 06:12:49nir.score({ probe: "blender-1", model: "cu-famA-v3" })
  8. 06:18:59ok blend end point reached · confidence bounds inside acceptance limit
  9. 06:19:00plc.write_setpoint({ tag: "FBD1.INLET_T", within: "design space" })
  10. 06:22:48ok loss-on-drying in target band · move logged to audit trail
  11. 06:22:49press.write_setpoint({ tag: "TP2.MAIN_FORCE", within: "design space" })
  12. 06:24:51ok weight and hardness on target · capping risk under threshold
  13. 06:24:52vision.stream({ cameras: 6, model: "visqa-defect-v2" })
  14. 06:27:10chip rate rising on camera 4 · attributed to spray rate, not tooling
  15. 06:27:11coater.write_setpoint({ tag: "CT1.SPRAY", within: "design space" })
  16. 06:29:14ok chip rate back to baseline · film window held
  17. 06:29:15nir.evidence_chain({ attributes: ["cu", "moisture"], method: "validated" })
  18. 06:29:53ok evidence chain assembled · citations attached
  19. 06:29:54approval.request({ action: "batch_release", reviewer: "QA" })
  20. 06:33:08ok approved by the named QA reviewer · identity and timestamp logged
  21. 06:33:09audit.write_release_package({ batch: "B-240918", genealogy: "full" })
  22. 06:34:01ok scenario complete · genealogy written · package cited

Reasoning trace

Plan, thought, action, observation, exactly as the orchestrator records it.

GoalRun one immediate-release tablet batch through granulation, co…

Run one immediate-release tablet batch through granulation, compression, coating and inspection inside the approved design space, with QA approval before release.

PlanRehearse on the twin first. Stop blending on NIR evidence rath…

Rehearse on the twin first. Stop blending on NIR evidence rather than on a fixed time. Trim drying, compression and coating only inside the approved design space. Inspect continuously. Hold release for the named QA reviewer, always.

ThoughtThe fixed recipe blends for a set time regardless of what the …

The fixed recipe blends for a set time regardless of what the spectra say. On the twin, the candidate that stops on evidence and trims inlet temperature before compression keeps content uniformity and moisture inside their limits with the lowest predicted capping risk.

Actiontwin.simulate(candidates=36) → candidate #14: evidence-based b…

twin.simulate(candidates=36) → candidate #14: evidence-based blend end point, bounded drying trim, compression force held inside the window, spray rate re-phased to bed temperature.

ObservationEvery candidate that pushed turret speed for takt raised predi…

Every candidate that pushed turret speed for takt raised predicted capping risk above the site threshold and was discarded. Rate is never traded for a quality attribute.

ActionExecute candidate #14 under autonomy level L2: five setpoint m…

Execute candidate #14 under autonomy level L2: five setpoint moves inside the design space, each logged. Batch release routed to QA.

ObservationChip rate rose on camera 4 at 06:27:10. Visqa attributed it to…

Chip rate rose on camera 4 at 06:27:10. Visqa attributed it to coating spray rather than tooling; a bounded spray-rate trim returned it to baseline in about two minutes.

OutcomeScenario complete. Every move inside the approved design space…

Scenario complete. Every move inside the approved design space, the QA approval recorded with identity and timestamp, and the cited release package written by Conforma to the immutable audit trail.

FAQ

Pricing questions

Cost, trial, ownership, risk and how to start.

Line tier $17,000 per compression, coating or granulation line per month; Plant tier $100,000 per month for the whole loop; Enterprise custom, landing between $750k and $10M annual contract value. Annual prepay saves 15 to 20%. Outcome components are available.

Guardrails

An agent that can move a compression force needs a leash

Pildeon writes to production equipment in a GMP plant. Every capability is scoped to the approved design space, every write is policy-checked, every action is written to an immutable Part 11 audit trail the site owns, and no agent can release a batch.

  • Bounded action space. Each agent can only write to an explicit setpoint allow-list, inside the limits the site's validation approved.
  • Policy engine before every write. Autonomy level, design-space limits, batch state, model version and reviewer assignment are all evaluated before a setpoint moves.
  • Human-in-the-loop gates. Batch release, any move outside the design space and any change to a validated parameter wait for a named QA reviewer.
  • Immutable audit trail. Append-only, hash-chained, exportable, retained on the site's own storage, with reviewer identity and timestamp on every decision.
  • Hard fallback. Loss of the edge node, the network or the model returns the line to the equipment's last known-good recipe.
  • Tenant and IP isolation. Formulations, recipes and models never cross a customer boundary. Validated on-prem deployment is available for regulated producers.

Compliance posture

Compliance and validation status
StandardScopeStatus
21 CFR Part 11Audit trail, e-signatures, records RUNNING Designed in from day one
GAMP 5Validation package for the platform RUNNING In progress, planned for the first design partners
cGMP · ICH Q8 to Q13Design space, QbD, continuous manufacturing RUNNING Design-aligned; site validation decides
SOC 2 Type ICloud control plane QUEUED Planned, first six months
SOC 2 Type IICloud control plane QUEUED Planned, months six to twelve
Data residencyValidated on-prem, air-gapped option SUCCEEDED Available by design

Read the security and validation overview

Enterprise

Standardise validated autonomy across the group

One policy model, one audit spine, one benchmark across every line in every plant, with formulation and tooling models kept private to each site.

Talk to the team Enterprise details

  • SSO, RBAC and named approvers down to the setpoint level
  • Group autonomy policy with per-site override and approval chains
  • Cross-plant benchmarking on yield, rejects, deviations and energy
  • Validated on-prem and air-gapped plant-edge deployment options
  • Validation packages and change-control records as first-class deliverables
  • Dedicated deployment engineer and quarterly model review per site
The first meeting

What each stakeholder asks first

Pildeon has no customer quotes to show yet, and will not invent any. These are the questions the three buyers in an OSD plant ask in the first meeting, and the answer each gets.

"What does this do to my reject rate, my deviation count and my release time, and how will you prove it on my line rather than on a slide?"

Site or manufacturing director · economic buyer

Answer: shadow mode first, baseline captured before any autonomous action, a written ROI target before a paid pilot.

"Will it ever move a setpoint outside the design space we validated, and can I see why it recommended every move it made?"

Formulation or process engineer (MSAT) · champion

Answer: no, by construction. Every recommendation carries its reasoning trace and its citation.

"Where is the Part 11 audit trail, who signs the release, and what happens to my validated state when the model changes?"

QA, quality and compliance lead · approver

Answer: an immutable audit spine, a named QA reviewer on every release, and every model change under GxP change control.

Get started

Start with one line

Shadow mode is free for design partners. The Line tier starts when the written metric says it should.