Licensing
Priced per clinic, quoted per clinic.
FertiliCore is enterprise clinical software, and it is sold that way: scoped against your unit, quoted in writing, with implementation costed separately rather than buried.
What the number depends on.
Four things move the figure materially. We would rather show you which ones they are than publish a price that turns out to be irrelevant to your situation.
The size of the unit
Annual cycle volume and the number of clinical sites under one licence. We do not price per named user — a clinic should never be choosing between a nurse having an account and saving money.
Which modules you run
A unit without an in-house genetics laboratory should not pay for one. The clinical core is a single licence; the reproductive-genetics module and the cryobank are scoped to what you actually operate.
Integrations you enable
Each connector you switch on carries a configuration and conformance effort against a specific partner system. Priced by the interface, once, rather than as an open-ended integration retainer.
Implementation and migration
Historical data conversion is the single largest variable and depends on the state of your existing system. We quote it separately and explicitly, after we have looked at your data rather than before.
In every licence
No feature gates on clinical safety.
The audit trail, the access controls and the tenant isolation are not a premium tier. Charging extra for the parts of a clinical system that protect patients would be an odd way to run a business.
- The full clinical record across all eleven domains
- Nine statistics dashboards and 33 printable report templates
- Twelve raw-data exports for offline and statutory analysis
- Role-based access control with the seeded clinical roles
- Multi-tenant isolation and the append-only audit trail
- Document attachment and retention
- Approval and notification engines
- English, Turkish and Arabic interfaces
- The integration platform — you enable the connectors you need
Commercial questions
Why is there no price on this page?
Because any number we published would be wrong for most readers. The gap between a single-site unit running 200 cycles a year without a genetics lab and a multi-site group running an in-house PGT service is large enough that a headline figure would mislead in both directions. We would rather scope it properly and give you a number you can take to a board.
Is it a subscription or a perpetual licence?
Both models are available and the choice usually follows how your institution prefers to account for the cost. An annual licence including support and updates is the most common arrangement; a perpetual licence with a separate maintenance agreement suits organisations with capital rather than operating budget.
Do you charge per user?
No. Per-seat pricing in a clinical setting quietly encourages account sharing, which destroys the value of an audit trail — if two embryologists work under one login, the record of who did what is worthless. Licensing per clinic removes that incentive entirely.
What does support include?
A named contact, an agreed response time, updates for the licensed period and help with the parts of an upgrade that touch your configuration. Because the deployment is yours, we agree an update schedule with you rather than pushing releases at you.
Can we run a pilot before committing?
Yes, and we prefer it. A time-boxed evaluation against your own historical data — not a canned demonstration dataset — tells you far more about whether the system fits your workflow, and tells us what your migration will actually involve.
Get a written quotation
Tell us your annual cycle volume, your sites, whether you run genetics in house and what you are migrating from. We will come back with a scoped figure rather than a range.