Technology at OVOO
A network product has to fit the way your teams deploy, secure and operate it. This page explains the engineering practices behind OVOO telecom and energy platforms; the product pages describe the service-specific capabilities.
Cloud‑native
A deployment needs a repeatable configuration, controlled traffic changes and a recovery route. Kubernetes, declarative infrastructure and release gates provide the mechanisms below.
Kubernetes & service mesh
Multi-AZ clusters, ingress, mTLS and traffic shaping, with right-sized capacity and autoscaling.
IaC & GitOps
Terraform/Ansible, declarative envs and drift detection.
Release controls
Blue-green releases, canaries, automated rollbacks and health gates. SRE practices and SLOs support operational review.
Security & Compliance
Security design connects data protection, operational access and evidence. Encryption in transit and at rest, isolated runtimes and managed secrets address different parts of that responsibility.
Encryption & keys
Protect transport and stored data with TLS, per-object keys and KMS/HSM integration.
Identity & access
Separate operational access from software provenance: SSO and least privilege govern people; signed releases and SBOMs identify the deployed software.
Compliance
Retention, access and audit policies provide evidence for the GDPR/KSeF and MiFID II requirements relevant to the service.
Digital identity: SSI & EUDI
Wallet credentials, issuer trust and OpenID protocols, integrated with operator IMS and SIP call control in Verified Caller ID.
SSI, DIDs & verifiable credentials
Wallet-held verifiable credentials, DID verification methods, signature validation and issuer trust.
EUDI wallet integration
Selected wallet profiles, credential attributes, relying-party authentication and issuer trust configuration.
OpenID credential exchange
OpenID4VCI for credential issuance; OpenID4VP for credential presentation to a verifier.
eSIM & Remote SIM Provisioning
Profile preparation, encrypted delivery and subscriber-system integration in OVOO SM-DP+.
Remote SIM Provisioning
SGP.22 v2.5, ES2+ profile orders and ES9+ device downloads.
Profile protection
ASN.1 encoding, certificate authentication and encrypted packages bound to an eUICC.
Subscriber integration
BSS controls profile orders; HSS integration links subscriber provisioning to profile creation. EAP-AKA belongs to the separate AAA access path after installation.
Open Source
Open components need an integration boundary and an operating model. We use maintained projects, explicit extension points and open tooling so product-specific code can coexist with those foundations.
Ecosystem first
Choose standards-based components and maintained communities as the basis for product integrations.
Extensible by design
Keep protocol adaptors, plugins and public APIs as explicit extension points rather than embedding every integration in service logic.
Transparent operations
Expose logs, metrics and traces through open tooling so operations can follow the product in their existing monitoring environment.
Distributed Ledgers
Usage and financial records may need evidence beyond a database export. Merkle proofs and public anchors provide tamper-evident verification; reconciliation compares records across the participating systems.
Merkle proofs
Batch → root → verifiable paths per record.
Public anchoring
Hedera/Ethereum anchors with cost controls.
Reconciliation
Deterministic diffs across billing/finance.
Technologies we build on
The selection below spans different products and integration needs; it is not a dependency list for every deployment.
- Kubernetes
- Docker
- Terraform
- Ansible
- Prometheus
- Grafana
- Jaeger
- Kafka
- PostgreSQL
- TimescaleDB
- Elastic
- Java
- Spring Boot
- Node.js
- Python
- Go
- REST
- GraphQL
- WebSockets
- WebRTC
- React
- Vue
- Angular
- TypeScript
- Tailwind CSS
- Cosmos
- Ethereum
- Hedera
- Hyperledger
- SSI
- DIDs
- Verifiable Credentials
- EUDI
- OpenID4VP
- OpenID4VCI
- eSIM
- SGP.22
- ES2+
- ES9+
- eUICC
- ASN.1
- Hotspot 2.0
- EAP-AKA
