Customer control without support tickets

SelfCare

SelfCare was crafted as Ankior's customer control plane. It makes organization structure, identity, billing, entitlements and support visible without pushing routine administration back to the provider.

Tenant control plane Tenant admin Identity Billing Support Backend Web app Cloud DevOps AI
Tenant overview

Introduction

Inside SelfCare

A multi-domain SaaS cannot scale if every user, invoice, entitlement and support change requires provider intervention.

What had to scale

The UX is admin-dense but calm: clear permissions, reversible setup steps and no hidden provider-only assumptions.

Self-service tenant operations RBAC governed access Billing customer visible Support case context

Features

Product features with technical depth

We separated customer control from provider operations and made entitlement, identity and billing workflows predictable.

Tenant structure

Organizations, locations and groups become manageable by customer admins.

Effective access

Roles, groups and direct grants are understandable before changes are saved.

Entitlement clarity

Domain activation and limits are visible as customer-facing product state.

Support context

Cases carry tenant, product and permission context from the start.

AI and automation readiness

The system keeps clean domain events and audit context for assisted workflows.

Admin dashboard

Customer admins see domains, access, billing and support health together.

Access review

Before granting access, the system explains effective permissions.

Provisioning path

New domain activation is explicit, traceable and support-aware.

Challenges

Scaling customer operations

Customer admins need power without being exposed to internal provider controls.

Technical challenges

01

Permission clarity

Admins had to understand effective access before changing roles, groups or grants.

02

Customer autonomy

Routine tenant operations needed to move out of provider support without exposing provider controls.

03

Billing context

Entitlements, invoices and support state had to stay understandable as one customer-facing product surface.

Domain challenges

01

Scaling customer operations

Customer admins need power without being exposed to internal provider controls.

02

Admin dashboard

Customer admins see domains, access, billing and support health together.

03

Access review

Before granting access, the system explains effective permissions.

Technology stack

Technology stack behind the product

SelfCare coordinates identity, tenant governance, billing profile, provisioning and support APIs while respecting source-domain ownership.

Backend .NET tenant and billing APIs
Identity Users, groups, roles, grants
Billing Profiles, invoices, payments
Support Cases, escalation, audit context
Web app Angular, TypeScript
Cloud GCP, Kubernetes, containers
DevOps CI/CD, OpenTelemetry, health checks
AI Assisted workflows and automation direction
.NET tenant and billing APIs groups grants invoices Cases audit context TypeScript Kubernetes CI/CD health checks Backend Billing Web app DevOps Tenant admin Users roles Profiles payments escalation Angular GCP containers OpenTelemetry Assisted workflows and automation direction Identity Support Cloud AI
Users roles Profiles payments escalation Angular GCP containers OpenTelemetry Assisted workflows and automation direction Identity Support Cloud AI .NET tenant and billing APIs groups grants invoices Cases audit context TypeScript Kubernetes CI/CD health checks Backend Billing Web app DevOps Tenant admin

Japonics

Give customers control without weakening governance

SelfCare shows how Japonics designs admin surfaces that are powerful without becoming chaotic.