Ankior Technologies / SAAS CONTROL PLANE

SelfCare

Ankior Technologies' tenant-facing control plane for organizations, users, permissions, billing, domain activation, and support.

Cloud Security
SelfCare preview
Client: Ankior Technologies Year: 2026

Identity and access control-plane architecture

Where the project started

SelfCare is the shared source of truth for tenants, employees, and permissions across the whole Ankior ecosystem, so no product domain has to duplicate its own identity and access logic.

Starting point

Without a self-service control plane every customer change becomes support work, a script, or a manual provider operation.

Direction taken

SelfCare is the source of truth for tenants, organizations, users, roles, permissions, entitlements, and billing context. Product domains do not replicate this logic; they consume controlled projections.

Business / Product

Problems and solutions

Each tile connects a real product tension with the decision that clarified the domain, UX, or operations.

Problem

Without a self-service control plane every customer change becomes support work, a script, or a manual provider operation.

Solution

Give customers a controlled model for organization, access, plans, and product activation.

Outcome Clean multi-tenant model
Problem

The scope could easily become a feature list without one product, data, and ownership model.

Solution

SelfCare is the source of truth for tenants, organizations, users, roles, permissions, entitlements, and billing context. Product domains do not replicate this logic; they consume controlled projections.

Outcome Tenant governance and domain provisioning
Problem

The project needed decisions that would stay readable after the first version: for users, the team, and further delivery.

Solution

Tenant governance and domain provisioning. Roles, groups, direct grants, and effective access.

Outcome Fewer provider-side manual operations

Roles and competencies

The competencies this build required

Competencies are shown as ownership roles: CTO, Tech Lead, engineering, DevOps, cloud, security, and AI where they were part of the work.

01

Fractional CTO

Connecting the product thesis, domain risk, and priorities so technology supports business decisions instead of becoming a separate workstream.

Open competency
Scope
  • Product category and positioning
  • Scope priorities and risk
  • Decisions ready for founder or CTO review
Applied experience
  • Product thesis translated into technical priorities.
  • Risks framed in a language stakeholders can review.
02

Tech Lead

Shaping responsibility boundaries, domain modeling, and architecture decisions so the project can grow without drifting into an accidental monolith.

Open competency
Scope
  • Bounded contexts and ownership
  • Readable technical decisions
  • Roadmap without implementation chaos
Applied experience
  • Domain boundaries and decisions that remain reviewable after MVP.
  • Ownership model readable for later delivery stages.
03

Software Engineer

Turning the domain into screens, APIs, flows, and maintainable implementation with focus on clarity and post-MVP evolution.

Open competency
Scope
  • Backend and application contracts
  • UX surfaces ready for iteration
  • Code and maintenance model
Applied experience
  • Implementation tied to the real product workflow.
  • Contracts and code prepared for post-launch iteration.
04

DevOps Engineer

Designing delivery, observability, and operations so release, diagnostics, and recovery are part of the product.

Open competency
Scope
  • CI/CD and release readiness
  • Observability and production signals
  • Operations without manual rituals
Applied experience
  • Release, diagnostics, and recovery designed as product capabilities.
  • Production signals ready for maintenance without guessing.
05

Cloud Engineer

Choosing cloud, data, and integration foundations so scale, cost, and reliability are not added after the fact.

Open competency
Scope
  • Google Cloud and managed services
  • Data, events, and storage
  • Cost and operational control
Applied experience
  • Cloud choices tied to cost, scale, and data responsibility.
  • Integrations and storage treated as foundations, not add-ons.
06

Security Engineer

Tenant isolation and explainable effective access (group, direct grant, inheritance) are the foundation, and high-risk actions require MFA or step-up verification.

Open competency
Scope
  • Tenant isolation as a foundation, not an add-on
  • Explainable effective access: group, direct grant, inheritance
  • MFA / step-up verification for high-risk actions
Applied experience
  • Privacy, roles, and auditability built into the product model.
  • Security visible in domain decisions, not only around the UI.

Stack by competency

Tech stack

The stack is grouped by competency so it shows both technology and responsibility: software, leadership, DevOps, cloud, security, and AI.

Software Engineer
  • .NET / ASP.NET Core
  • .NET MAUI mobile client
  • Angular web client
  • PostgreSQL
Tech Lead
  • Identity governance
  • Access-control governance
  • Entitlement & billing boundaries
  • Integration governance
  • Multi-tenant domain model
DevOps Engineer
  • OpenTelemetry
  • Cloud Logging
Security Engineer
  • OIDC
  • RBAC
  • Tenant isolation
  • MFA / step-up verification
.NET / ASP.NET Core Angular web client Identity governance Entitlement & billing boundaries Multi-tenant domain model Cloud Logging RBAC MFA / step-up verification Billing integrations Angular .NET / ASP.NET Core Angular web client Identity governance Entitlement & billing boundaries Multi-tenant domain model Cloud Logging RBAC MFA / step-up verification Billing integrations Angular .NET / ASP.NET Core Angular web client Identity governance Entitlement & billing boundaries Multi-tenant domain model Cloud Logging RBAC MFA / step-up verification Billing integrations Angular
.NET MAUI mobile client PostgreSQL Access-control governance Integration governance OpenTelemetry OIDC Tenant isolation .NET 8 .NET MAUI Effective access resolution .NET MAUI mobile client PostgreSQL Access-control governance Integration governance OpenTelemetry OIDC Tenant isolation .NET 8 .NET MAUI Effective access resolution .NET MAUI mobile client PostgreSQL Access-control governance Integration governance OpenTelemetry OIDC Tenant isolation .NET 8 .NET MAUI Effective access resolution