HeliosDB Integration Certification Criteria
| Item | Detail |
|---|---|
| Document | Integration Certification Criteria |
| Version | 1.0 |
| Effective date | 2026-10-29 |
| Published by | Dimen Sigon OÜ, trading as HeliosDB, registry code 16757774, Ahtri 12, 10151 Tallinn, Estonia |
| Address of this document | https://partners.heliosdb.com/legal/certification-criteria |
Change log
| Version | Date | Change |
|---|---|---|
| 1.0 | 2026-10-29 | First published version. |
1. What certification means
1.1 HeliosDB certification states that a named version of a partner's product (an "Integration") has passed the tests in these criteria against named HeliosDB versions. It is a factual statement about tested versions. It is not an endorsement of the partner's product, a warranty of the Integration, or a support commitment by HeliosDB for the partner's product.
1.2 Certification is free of charge for partners in the HeliosDB partner programme. It creates no obligation for either party to buy, sell or pay anything.
1.3 No partner may use a certification name, badge or statement until HeliosDB has issued a certificate under these criteria.
2. Who can apply
2.1 A partner with a signed HeliosDB technology, ISV or hosting partner agreement may apply through the Partner Portal, naming the Integration, its version, the HeliosDB editions and versions it targets, and the interfaces it uses.
3. Criteria
3.1 An Integration is certified only if all of the following are met for each HeliosDB edition and version named in the certificate:
| No. | Criterion | Evidence |
|---|---|---|
| C1 | Supported interfaces only. The Integration uses only interfaces, protocols and drivers that the Release and Capability Matrix lists for that edition and version as tested-supported or supported-with-limitations, within the stated limitations. | Interface list mapped to Matrix rows |
| C2 | Generally Released versions. Tests run against Generally Released HeliosDB versions, not preview, nightly or source builds. | Version identifiers in the test report |
| C3 | Functional tests. A reproducible test suite covers connection and authentication, the reads and writes the Integration performs, parameter binding and types, transactions where the Integration uses them, and error handling, with normal-path and error-path cases. | Test suite source or a runnable package, and the results |
| C4 | Durability behaviour. Where the Integration writes data, it treats a write as successful only after the database acknowledges the commit, and it does not report success for a write whose outcome is unknown. | Test cases and a short description |
| C5 | Security baseline. The Integration supports TLS to HeliosDB, does not require trust or password-less authentication on non-local connections, does not store HeliosDB credentials in clear text, and follows the security settings in the Documentation. | Configuration description and test results |
| C6 | Documentation. The partner publishes installation and configuration instructions naming the certified versions, the limitations from the Matrix that affect users, and the partner's own support contact. | Links |
| C7 | Support and escalation contact. The partner names a technical contact for joint problem diagnosis and a security contact. | Contacts in the Partner Portal |
| C8 | Accurate statements. The partner's descriptions of the Integration and of HeliosDB comply with the HeliosDB Brand Guidelines and the partner agreement, and state HeliosDB capability only as listed in the Matrix. | Draft listing and materials |
3.2 HeliosDB reruns or reviews the tests, or a representative subset, before issuing a certificate. HeliosDB decides within 20 business days after receiving complete evidence, and gives reasons for a refusal with the criteria not met.
4. The certificate
4.1 Each certificate states: the partner; the Integration and its version; the HeliosDB editions and versions tested; the Matrix version used; the criteria version (this document's version); the issue date; and the expiry date.
4.2 A certificate expires twelve months after issue, or earlier if the partner releases a new major version of the Integration or HeliosDB ends support for a certified HeliosDB version.
4.3 Certificates are listed in the Partner Portal and may be listed on www.heliosdb.com.
5. Maintenance and recertification
5.1 When HeliosDB makes a new supported minor version Generally Released, the partner tests the Integration against it within 60 days and reports the result. The period is extended where the HeliosDB build is unavailable or defective, or where the scope changes, as agreed with HeliosDB.
5.2 Recertification uses the criteria version current at the time. The partner may apply for recertification up to 60 days before expiry; the existing certificate stays valid until HeliosDB decides.
5.3 HeliosDB gives at least 90 days' notice before removing an interface that a current certificate relies on, except for urgent legal or security reasons, in which case it gives notice as soon as possible with a mitigation plan.
6. Suspension and withdrawal
6.1 HeliosDB may suspend or withdraw a certificate if: the Integration no longer meets a criterion and the partner does not remedy it within 30 days of notice; a serious security defect in the Integration is not fixed within a reasonable time; or the partner breaches the brand or marketing provisions of its agreement. HeliosDB gives reasons in writing.
6.2 When a certificate expires or is withdrawn, the partner stops using the certification name and badge within 30 days, except in factual, dated historical references.
7. Use of the certification name
7.1 A certified partner may say "Certified for HeliosDB [edition] [versions]" for the certified Integration version only, and may use the certification badge supplied in the Partner Portal, under the HeliosDB Brand Guidelines. It must not apply the statement to other products or versions.
8. Changes
8.1 HeliosDB may publish new versions of these criteria. A new version applies to applications and recertifications started after its effective date; a certificate issued under an earlier version stays valid until it expires. Every version is published at the address at the top with its version, effective date, change log and SHA-256 fingerprint.