Ankior Technologies / PROVIDER OPERATIONS
Backoffice
Ankior Technologies' provider-facing operations platform for diagnostics, replay, support, rollouts, governance, and privileged operations.
Provider operations without unaudited shortcuts
Where the project started
Backoffice aggregates provider-side operations across five Ankior domains while keeping explicit domain ownership through module prefixes, so support and diagnostics never bypass tenant boundaries.
Backoffice aggregates provider-side workflows while preserving explicit domain ownership through module prefixes. Privileged actions require reason, approval, and audit, while diagnostics use replay and projections instead of direct data editing.
Business / Product
Problems and solutions
Each tile connects a real product tension with the decision that clarified the domain, UX, or operations.
A multi-domain SaaS without backoffice drifts into manual scripts, database access, and unaudited support.
Design an internal operations center without violating tenant isolation.
The scope could easily become a feature list without one product, data, and ownership model.
Backoffice aggregates provider-side workflows while preserving explicit domain ownership through module prefixes. Privileged actions require reason, approval, and audit, while diagnostics use replay and projections instead of direct data editing.
The project needed decisions that would stay readable after the first version: for users, the team, and further delivery.
Diagnostics and replay instead of manual fixes. Privileged action logging and approval.
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.
Fractional CTO
Connecting the product thesis, domain risk, and priorities so technology supports business decisions instead of becoming a separate workstream.
Open competency- Product category and positioning
- Scope priorities and risk
- Decisions ready for founder or CTO review
- Product thesis translated into technical priorities.
- Risks framed in a language stakeholders can review.
Tech Lead
Shaping responsibility boundaries, domain modeling, and architecture decisions so the project can grow without drifting into an accidental monolith.
Open competency- Bounded contexts and ownership
- Readable technical decisions
- Roadmap without implementation chaos
- Domain boundaries and decisions that remain reviewable after MVP.
- Ownership model readable for later delivery stages.
Software Engineer
Turning the domain into screens, APIs, flows, and maintainable implementation with focus on clarity and post-MVP evolution.
Open competency- Backend and application contracts
- UX surfaces ready for iteration
- Code and maintenance model
- Implementation tied to the real product workflow.
- Contracts and code prepared for post-launch iteration.
DevOps Engineer
Designing delivery, observability, and operations so release, diagnostics, and recovery are part of the product.
Open competency- CI/CD and release readiness
- Observability and production signals
- Operations without manual rituals
- Release, diagnostics, and recovery designed as product capabilities.
- Production signals ready for maintenance without guessing.
Cloud Engineer
Choosing cloud, data, and integration foundations so scale, cost, and reliability are not added after the fact.
Open competency- Google Cloud and managed services
- Data, events, and storage
- Cost and operational control
- Cloud choices tied to cost, scale, and data responsibility.
- Integrations and storage treated as foundations, not add-ons.
Security Engineer
Privileged actions require approval and dual-control, and diagnostics rely on replay and projections instead of directly editing customer data.
Open competency- Approval and dual-control for privileged provider actions
- Diagnostics via replay and projections, not production data edits
- Least-privilege provider RBAC with a full action audit trail
- 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.
- .NET / ASP.NET Core
- .NET MAUI mobile client
- Angular web client
- PostgreSQL
- Event-driven integration
- Access-control governance
- Analytics & projection boundaries
- OpenTelemetry
- Cloud Logging
- Kafka operations
- Kafka
- RBAC
- Audit log
- Dual-control approval
- Profile projections
Product preview
Gallery
Selected screens and materials showing the product surface, UX decisions, and work outcome.