All charges are applied per device — regardless of whether multiple devices share the same server, the same local machine, or the same hybrid connector installation.
1. API Activation & Yearly License — required for every device
Every biometric device communicating through our gateway requires an active API. This involves two distinct charges.
API Activation is a one-time setup charge that enables the API for that device. Once activated, the device is permanently registered in our system with no expiry on the activation itself.
API Yearly License defines how long the device can actively push data through the gateway. It can be purchased in flexible durations — from one year through to lifetime — based on your operational needs.
These two charges apply to every device individually. If you have ten devices connected through a single server or a single hybrid connector installation, each of those ten devices carries its own Activation and License.
Renewal & Expiry Rules
If you renew before the license expires, only the License cost applies. The validity period is calculated from the start date of the previous license to the end date of the new one — meaning no time is wasted and the renewal seamlessly extends the existing period.
If the license has expired and you renew without needing the data generated during the gap period, only the License cost applies. The new validity begins from the renewal date.
If the license has expired and you need access to data generated between the expiry date and the renewal date, Activation will be applied again for that device to recover and sync the gap period data.
2. Protocol Update — for verified third-party machines
If you are integrating a third-party biometric device that is already verified and listed on our developer portal (developer.camsbiometrics.com), a Protocol Update charge applies per device.
This covers the work required to align the verified device with our biometric gateway protocol, ensuring seamless and standards-compliant communication with our infrastructure. Even if multiple verified devices of the same model are being connected, the Protocol Update is charged per device.
3. Hybrid Connector — for non-verified third-party machines
For biometric devices not on our verified list, a Hybrid Connector charge applies. This covers building a custom integration bridge between the device and our gateway.
Depending on your environment, the connector takes one of two forms:
- Hybrid Push Service — a lightweight service installed locally on the client machine, which can serve multiple devices connected to that machine
- Dedicated Connector — connects one or multiple databases or devices directly from our gateway server
It is important to note that even when a single Hybrid Push Service installation serves multiple devices on one machine, or a single Dedicated Connector handles multiple devices from the gateway server, the API Activation and License charges still apply individually to every device passing data through that connector.
4. Software Integration — standard API carries no additional cost
If your software is built to consume our standard API structure (camsbiometrics.com/application/biometric-web-api.html), no additional integration cost applies.
If your software requires data in a non-standard format — a custom payload structure, a bespoke response schema, or a proprietary connector format — an integration cost for that specific software will apply.
Quick Reference
- Every device → API Activation + Yearly License, charged per device
- Verified third-party machine → Protocol Update charge, per device
- Non-verified third-party machine → Hybrid Connector charge, per device
- Multiple devices on one server or one connector → each device still charged individually
- Standard API format software → No additional cost
- Custom format software → Integration cost applies
- Renewal before expiry → License cost only, validity extended from last start date
- Renewal after expiry, no gap data needed → License cost only, validity starts from renewal date
- Renewal after expiry, gap data required → Activation applied again per device
