Ankior Technologies / SAFETYTECH

AssetsManager

A platform for critical assets, inventory, storage units, physical access, inspections, and replenishment.

System design Cloud Security
AssetsManager preview
Client: Ankior Technologies Year: 2026

Auditable access control for critical assets

Where the project started

AssetsManager treats asset history as an evidence layer: no inventory correction ever overwrites the past, and physical access to cabinets and rooms stays independent of any single lock vendor.

Starting point

Organizations do not know whether a critical asset is available, who accessed it, and whether its history can be audited.

Direction taken

AssetsManager separates assets, inventory, storage units, accesses, inspections, and replenishment. A cabinet can be both a storage unit and an access point, while asset history remains an evidence layer.

Business / Product

Problems and solutions

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

Problem

Organizations do not know whether a critical asset is available, who accessed it, and whether its history can be audited.

Solution

Create a tenant-safe inventory truth for assets, locations, access, events, and evidence.

Outcome Clear asset/inventory/access boundaries
Problem

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

Solution

AssetsManager separates assets, inventory, storage units, accesses, inspections, and replenishment. A cabinet can be both a storage unit and an access point, while asset history remains an evidence layer.

Outcome Vendor-agnostic access control
Problem

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

Solution

Vendor-agnostic access control. Immutable asset and inventory history.

Outcome Model ready for IoT and warehouses

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

Physical access is controlled independently of any smart-lock vendor, and asset history is append-only, with explicit compensating entries instead of silent edits.

Open competency
Scope
  • Vendor-agnostic access control (RFID/BLE/NFC/PIN/override)
  • Append-only asset history with explicit compensating entries
  • Auditable emergency override instead of hidden access
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
  • Event-driven integration
  • Access-control governance
  • Evidence & history domain model
  • Offline-first domain model
  • Vendor-agnostic integration model
DevOps Engineer
  • OpenTelemetry
  • Cloud Logging
  • Kafka operations
Cloud Engineer
  • Kafka
Security Engineer
  • RBAC
  • Audit log
  • Vendor-agnostic access control
  • Auditable emergency override
.NET / ASP.NET Core Angular web client Event-driven integration Evidence & history domain model Vendor-agnostic integration model Cloud Logging Kafka Audit log Auditable emergency override Smart lock adapters .NET MAUI Append-only asset history .NET MAUI mobile client PostgreSQL Access-control governance Offline-first domain model OpenTelemetry Kafka operations RBAC Vendor-agnostic access control .NET 8 Mobile offline sync Angular .NET / ASP.NET Core Angular web client Event-driven integration Evidence & history domain model Vendor-agnostic integration model Cloud Logging Kafka Audit log Auditable emergency override Smart lock adapters .NET MAUI Append-only asset history
.NET MAUI mobile client PostgreSQL Access-control governance Offline-first domain model OpenTelemetry Kafka operations RBAC Vendor-agnostic access control .NET 8 Mobile offline sync Angular .NET / ASP.NET Core Angular web client Event-driven integration Evidence & history domain model Vendor-agnostic integration model Cloud Logging Kafka Audit log Auditable emergency override Smart lock adapters .NET MAUI Append-only asset history .NET MAUI mobile client PostgreSQL Access-control governance Offline-first domain model OpenTelemetry Kafka operations RBAC Vendor-agnostic access control .NET 8 Mobile offline sync Angular