β—†Nikanity

Design, Build & Govern every Cloud, Data & AI estate.

A single system of record to design, build & govern. Connect strategy, architecture, cloud inventory, cost visibility and governed AI assistance. Capabilities that are still on the roadmap are labelled as such.

Multi-cloud inventory (AWS, Azure, GCP) Confirm-first cloud actions Governed Word architecture documents Cost visibility from connected billing feeds
πŸ”’ Enterprise SSO (Microsoft Entra ID & Google sign-in) • Privacy & Cookie Governance
ILLUSTRATIVE CONTEXT: US-EAST-PRIMARY (SAMPLE)
● SAMPLE VIEW
Sample secure score
Illustrative
Not a customer measurement
Sample cost view
Illustrative
Connect billing to see real figures
Microsoft Azure (sample subscription) Sample finding
AWS Organizations (sample account) Sample finding
GCP Projects (sample project) Sample status
Connected & Planned Ecosystem
☁️ Microsoft Azure
🟧 Amazon Web Services
🌐 Google Cloud
πŸ–₯️ VMware vSphere
⚑ Databricks (planned)
πŸ“‹ ServiceNow (planned)
πŸ“ Terraform Modules
☸️ Kubernetes Estates
DOMAIN 01 GUIDED
Strategy & Architecture
Business cases, wave planning and architecture documents from your own answers.
DOMAIN 02 PARTIAL
Build & Automate
Governed IaC proposals and catalogue services. Account vending covers base resource types.
DOMAIN 03 PARTIAL
Secure & Govern
Posture findings from connected clouds. Framework mapping is in progress.
DOMAIN 04 PARTIAL
FinOps & Operations
Cost visibility from connected AWS and Azure billing feeds. GCP billing is on the roadmap.

Core Platform Capabilities

A modular suite that brings architecture, platform engineering, service operations and finance into one system. Each capability states what works today.

⚑

Multi-Cloud Account Vending

Provision landing-zone accounts and subscriptions from governed Terraform modules. Vending currently covers base resource types; broader coverage is on the roadmap.

  • Terraform-first IaC modules through reviewed catalogue services
  • Policy-as-code guardrails on generated templates
  • Roadmap: landing-zone vending beyond base resource types
πŸ“‹

Change & Governance Records

Record changes, approvals and governance evidence against connected resources. Full ITSM workflows are not available today.

  • Approval records for IaC generation and catalogue reviews
  • Governance risks, policies and evidence links
  • Not possible today: Pre-CAB gates, Known Error Database, ServiceNow sync
πŸ—„οΈ

Multi-Cloud Inventory

Read-only discovery of compute, storage, database, network and backup resources across connected AWS, Azure, GCP, VMware and OpenStack estates.

  • Inventory refreshes on sync, not in real time
  • Resource relationships where the provider reports them
  • Not possible today: automatic drift healing
πŸ›‘οΈ

Cloud Security & Governance

Posture findings from connected Azure Defender and Policy feeds and AWS and GCP checks, with NIST CSF 2.0 mapping in progress.

  • Findings from connected security feeds
  • Framework mapping (NIST CSF 2.0, CIS Controls v8, PCI DSS v4.0) in progress
  • Roadmap: broader AWS posture checks
πŸ’°

Cloud Cost Visibility

Cost views from connected AWS and Azure billing feeds, with budget records. GCP billing export and rightsizing recommendations are on the roadmap.

  • AWS and Azure billing feeds
  • Budget records and cost allocation views
  • Roadmap: GCP billing and invoice reconciliation
πŸ“

Strategy & Architecture (S&A)

Turn strategy answers into business cases, modernisation waves and architecture documents, reviewed by people before approval.

  • Business case and cost comparison models
  • Architecture and strategy documents drafted from saved answers
  • Human approval before any document is treated as final

Governance Across Cloud, Data & AI Estates

Connect architectural reference patterns, posture findings and cloud spend into one control view. The examples below are illustrative, not customer data.

(ILLUSTRATIVE EXAMPLES, NOT ACTUAL)
Category Platform & System Resource Scope Example Finding Example Severity Example Recommended Action Action Status
Public Cloud Microsoft Azure /subscriptions/sample-01 Excessive standing administrator role assignments HIGH Reduce role scope and review assignments Review by a person
Private Cloud VMware vSphere vcenter.example.internal/cluster-01 Management network segmentation review needed HIGH Review network segmentation with the platform team Review by a person
Data Platforms Databricks on AWS (planned) catalog:sample_gold Access grants not verified against policy MEDIUM Compare grants with the approved access model Not connected today
AI Platforms Azure OpenAI Service endpoint:sample-deployment No token budget defined MEDIUM Define a budget owner and monthly limit Token telemetry on roadmap
SaaS Platforms ServiceNow ITSM (planned) instance:sample/cmdb Resources not present in a service catalogue MEDIUM Reconcile the list manually today Sync not available
Notice: These examples are illustrative, not actual findings. Real findings appear after you connect your own accounts and complete a sync. Nikanity control view

Nikan AI: Platform & Customer Assistance

Specialist assistants that draft, explain and propose, with confirm-first human approval before any change is made.

TIER 01: PLATFORM ASSISTANCE

Platform-Level Nikan AI

Assistance that answers questions about the platform, explains its recorded data and points to the right workspace, without exposing one customer's data to another.

TIER 02: CUSTOMER ASSISTANCE

Customer-Level Specialist Assistants

Specialists that work within each customer's own records to help draft strategy and architecture content, explain findings and propose actions. Each proposal waits for a person to approve it.

SERVICE MANAGEMENT
Current scope: Approval records and governance evidence are kept in Nikanity. Full ITSM workflows, Pre-CAB gates and ServiceNow synchronisation are not available today and are not claimed here.
PRIVATE MODEL ENDPOINTS
Approved providers: Platform configuration supports approved model providers, including OpenAI-compatible endpoints. Data-handling terms depend on the provider you approve; no zero-leakage guarantee is made.

From Strategy to Operations

Keep executive roadmaps, architecture, delivery and operations linked in one place.

STAGE 01
Strategy & Investment
Build business cases with cost comparisons and multi-year adoption milestones from your own inputs.
Business cases: Available
STAGE 02
Target Architecture
Document target-state architecture and decisions. Continuous drift measurement against live estates is not available today.
Drift measurement: Not available
STAGE 03
Governed Build
Generate reviewed Terraform proposals and catalogue services. Provisioning and apply run only through approved workflows.
Approval: Required
STAGE 04
Continuous Operations
Review inventory, posture findings and cost views from connected accounts, with confirm-first actions on virtual machines.
Actions: Confirm-first

Two Customer Deployment Models

Whether you are governing your own cloud estate or delivering managed cloud services to several clients.

OPTION 01 • ENTERPRISE ORGANIZATIONS

End Customer Model

A single-customer workspace for enterprise CCoE, platform engineering, security and architecture teams that want one governed view of their own estate.

  • Single-customer workspace with its own sign-in boundary
  • Read-only inventory from connected cloud accounts
  • Confirm-first actions on virtual machines
  • Documents and business cases drafted from your own answers
  • Connected private model endpoints where your organisation approves them
OPTION 02 • MANAGED SERVICE PROVIDERS

System Integration & MSP Edition

For managed service providers and system integrators who run governed cloud services for several clients from one platform, with each client's data kept in its own tenant.

  • Tenant-scoped data separation enforced by database access rules
  • Shared service and script catalogue distribution (in governed review)
  • Per-client cost views from connected billing feeds
  • Roadmap: co-branded client portals

Built for End Customers & System Integrators

Each customer's records are scoped to its own tenant through database access rules that are tested on every release. Isolation is verified by automated tests; it is not a certification.

Tenant-scoped Access rules
Tested Isolation checks
Audit Recorded actions
ILLUSTRATIVE TENANT LIST Sample only
◆ CLIENT: EXAMPLE CLIENT A TENANT A
◆ CLIENT: EXAMPLE CLIENT B TENANT B
◆ CLIENT: EXAMPLE CLIENT C TENANT C

Enterprise Pricing

Choose the commercial model that fits your operating model, by customer deployment or by functional module. Pricing is agreed with sales.

Service Providers
System Integration & MSP Edition
Multi-tenant platform for integrators and MSPs managing several client accounts.
Partner / agreed with sales
  • Tenant-scoped separation for each client
  • Shared service and script catalogue distribution (in governed review)
  • Per-client cost views from connected billing feeds
  • Roadmap: co-branded client portals
Talk to Sales →
Framework mapping (in progress, not certification):
NIST CSF 2.0 CIS CONTROLS V8 PCI DSS V4.0