TRUST & SECURITY
Built for trust.
Designed for control.
Taranga is designed to help telecom operators modernise their commercial systems while keeping security, data control, operational responsibility and accountable automation at the centre of the architecture.
Security and trust shape how business capabilities, users, integrations and AI agents operate.
Opens an editable email draft. No request is sent or meeting reserved.
Security by design
Defined access. Clear boundaries.
The commercial platform’s security approach centres on service boundaries, tenant isolation, identity-aware access and controlled integrations. Human users, APIs and software agents need explicit authority within the relevant tenant and business context.
The Architecture page describes tenant-scoped identities, component-level token validation and PostgreSQL row-level security. Validate the implementation and configuration against the intended deployment, including cross-tenant access and privileged operations.
Privacy & sovereignty
Your data. Your environment. Your control.
Operators have different data-residency, operational and regulatory obligations. Define where information is processed, who can access it and which external services participate in the deployment.
Sovereign deployment when you need it. Taranga can be deployed as a sovereign solution, running and operated entirely within your chosen European country. The sovereign deployment scope is agreed and validated for each project, including AI services, external integrations and support access.
Self-managed, managed and SaaS arrangements allocate responsibilities differently. Hosting location alone does not establish privacy compliance; data flows, access policies and contractual arrangements must fit the project.
Governed AI
Automation within defined business boundaries.
AI can accelerate commercial operations, but consequential decisions require authority, policy and accountability. Define agent permissions, executable preconditions, approval requirements and oversight appropriate to the action.
The Architecture page describes registered actions with typed inputs, role permissions and approval requirements. Assess their coverage, failure handling and escalation for the selected use case. Useful automation should preserve operator control.
Illustrative policy examples include discount limits, approval before pricing publication, financial thresholds for billing adjustments and scoped access to accounts and services. These examples do not establish current implementation of each rule.
Deployment & resilience
Operate on your terms.
Taranga is source-available under a commercial licence, not open source. Self-managed customers operate their environment and may purchase maintenance, product updates and support separately. Managed and SaaS arrangements define different responsibilities contractually.
Request access to a free evaluation snapshot with no evaluation time limit. The evaluation is a point-in-time release without ongoing product updates. Production use, updates and support are governed by applicable commercial terms.
For each deployment, agree responsibility for environment security, identity configuration, monitoring, backup and recovery, incident handling and integrations. Assess recovery testing and service commitments for the contracted scope. No universal availability, RPO or RTO commitment is stated here.
CHANNELS & CHARGING
Responsibilities follow the selected architecture.
Taranga provides the commercial BSS core and customer channels. Customers may retain their own channels or combine them with Taranga-delivered experiences. Charging is supplied externally, using a lightweight open-source solution or an existing platform.
Security, privacy, monitoring, incident handling and support responsibilities must cover the selected channels, charging solution and integration boundaries. Taranga’s commercial source-available licence is separate from the external charging solution’s licence.
Standards & assurance
Industry interfaces. Clearly scoped assurance.
The Architecture page describes TM Forum Open API payloads and conformance assessment using the applicable test kits. API versions, coverage and conformance results need evidence tied to the tested implementation and execution date.
Architecture alignment and API conformance are distinct from formal certification. Security and privacy assessment depends on implemented controls, deployment context, customer obligations and applicable independent assurance. No ISO, SOC 2, TM Forum certification or blanket regulatory compliance claim is made on this page.
Transparency & auditability
Know what happened and under whose authority.
The Architecture page describes execution receipts and captured outcomes for governed actions. Receipt generation is distinct from demonstrating a complete audit capability.
For the intended use case, establish which identities, permissions, policy decisions, inputs, approvals, execution results and business outcomes are recorded. Validate retention, tamper resistance, completeness, retrieval and customer visibility before relying on those records for assurance.
DecisionReceipt and ActionReceipt are proposed patterns for organising this evidence. Their names do not establish a delivered audit product or guarantee coverage of every decision.
YOUR NEXT MOVE
Discuss the requirements that matter to you.
Bring your deployment context, questions and assurance needs. We can discuss the relevant technical information and agreed responsibilities.
Opens an editable email draft. No request is sent or meeting reserved.