# Platforms

> Platform engineering from Boltcliq: secure multi-tenant platforms, APIs and developer experience that unify data, models and teams, on Boltcliq products or your own stack.

Canonical URL: https://www.boltcliq.com/solutions/platforms
Part of: https://www.boltcliq.com/llms.txt

Operating platforms that bring data, models and teams into one place.
- Organizations run on dozens of disconnected tools. A platform gives analysts, operators and agents one place to work, with the same data and the same permissions.
- Unified: One place for data, workflows and models
- Multi-tenant: Designed for several teams, units or customers
- Extensible: APIs and tooling for your own developers
- Long-term: Built for ownership over years, not a launch
### What we do
- A platform is the layer between your systems and the people and agents who use them. It holds shared services such as identity, data access, workflow, notification and audit, so each new application does not rebuild them. Done well, the tenth application takes a fraction of the effort of the first.
- We design platforms around the way your organization works. That includes tenants and permissions for several business units or customers, a catalogue of data and services, environments for development and production, and tooling that lets your developers build safely. We also design the boundaries: what the platform team owns, and what product teams own.
- Whether you adopt Boltcliq products or extend your own stack, we deliver the engineering to make the platform production grade. That means security review, reliability targets, documentation, upgrade paths and a support model. We aim for a platform your team can own for years, not one that depends on us.
### One place to work
- People lose hours to switching between tools, asking for access and reconciling copies of the same data. A platform removes much of that friction by giving every team the same entry point, identity and data catalogue.
- It also changes how fast you can build. Once identity, data access, audit and deployment are provided, a team can launch a new internal application or a customer service in weeks.
- One identity and one access model
- A catalogue of data and services
- Paved paths for building and deploying
### Capabilities
**Platform engineering**
- We design and build the core services: tenancy, identity integration, data access, workflow, notification and audit. Services are versioned, documented and observable. We set reliability targets and support rules with the team that will run them.
- Shared services with clear owners
- Reliability targets and runbooks
- Upgrade and deprecation policy
- Shared services are only shared if they are dependable.
**Multi-tenant design**
- We build isolation between business units, subsidiaries or customers at the data, compute and permission layers. Each tenant has its own policies, quotas and audit trail. Central teams can see aggregated views without seeing private data.
- Tenant-level data isolation
- Quotas and policy per tenant
- Aggregate views for central teams
- Groups and service providers need separation they can prove.
**APIs and integration**
- We define clean interfaces between your systems, partners and agents. We design APIs with consistent patterns, authentication, rate limits and versioning, and build adaptors for older systems. Events and webhooks keep integrations current.
- REST, GraphQL and event interfaces
- Adaptors for legacy systems
- Versioning and developer documentation
- Integration debt is what slows platforms down.
**Developer experience**
- We give your developers templates, local environments, test data, pipelines and a portal that explains how to build on the platform. Guardrails are built in, such as security scanning and policy checks, so teams move quickly and stay inside the rules.
- Project templates and paved paths
- Test data and sandboxes
- Automated policy and security checks
- Good tooling is the cheapest governance.
**Workflow and applications**
- We build workflows that mix human and automated steps, with approvals, escalation and service levels. Applications include queues, forms and views for staff and customers, designed for low bandwidth and mobile where needed.
- Human and agent workflow steps
- Approvals and escalations
- Mobile and low-bandwidth interfaces
- Platforms earn their keep in daily work.
**Security and operations**
- We build identity, secrets, audit and monitoring into the platform. We run security reviews, test recovery and write the operating model for platform and product teams. Observability covers cost, latency and quality.
- Identity, secrets and audit built in
- Monitoring and incident process
- Recovery tests
- A platform concentrates risk, so it must concentrate care.
### Where it applies
- Banking groups
- A group with subsidiaries in several countries runs separate systems and cannot share tools or analytics safely.
- A multi-tenant platform gives each subsidiary its own data and policy, with common services and group-level reporting.
- Group and country risk officers decide what is shared across borders.
- Telecommunications
- An operator has separate teams building apps for mobile money, customer care and network operations.
- A common platform offers identity, data access and workflow so teams ship faster and consistently.
- Product leaders decide priorities. The platform team decides standards.
- Government
- Agencies want to offer digital services but each builds its own identity, payments and records.
- A government platform offers shared services, with each agency keeping control of its own data and rules.
- Agencies decide on data sharing within the law. Central bodies set standards.
- Agriculture and commodities
- A trader works with cooperatives, transporters and buyers and wants a shared place to track lots and payments.
- A platform offers each party a view of the shared lot data, with permissions and audit.
- Each party decides what it shares. The operator decides rules for disputes.
### Built on
**Argus**
- Provides the runtime, environments, storage and sandboxes that platform services and applications run on.
- Boltcliq product
- A ready base for new applications.
**Odin**
- Supplies identity, authentication and authorization for every tenant, service and agent.
- Boltcliq product
- Access is consistent across the platform.
**Zeus**
- Adds the shared ontology, governed metrics and workflow design to the platform.
- Boltcliq product
- Every application shares one model of the business.
### What we do and do not do
- Design and build platform services with your engineers
- Define tenancy, access and API standards
- Build developer tooling and documentation
- Operate with you until your team is ready
- Use Boltcliq products or your existing stack
- Force a rewrite of every system
- Build a platform nobody asked to use
- Hide the code or the architecture
- Create a permanent dependency on us
- Skip security review for speed
### Questions we hear
- Do we need a platform or just an application?
- If several teams or tenants need the same services, a platform pays off. For one application, we will say so. We prefer to start with the smallest platform that serves a real second team.
- Can you build on our existing stack?
- Yes. We work with the languages, clouds and tools you already use. Boltcliq products are an option, not a requirement.
- How do you handle tenants and data separation?
- Isolation is designed at data, compute and permission layers, and tested. Which isolation level is needed depends on your risk and the rules that apply, so confirm with counsel.
- Who owns the platform?
- You do. We build in your accounts and repositories, and train a platform team to run it.
- How long does it take?
- A first useful version can appear within a few months. We plan in stages so a team is using it early.