Ankior Technologies / SAFETYTECH

SafetyOps

An EHS platform for incidents, investigations, CAPA, risk, tasks, evidence, and auditable closure.

System design Development Security
SafetyOps preview
Client: Ankior Technologies Year: 2026

Closed-loop safety operations architecture

Where the project started

SafetyOps carries an incident from intake through triage, RCA, and CAPA to a verified closure, with an immutable timeline and evidence built to survive an audit.

Starting point

Incidents without owners, evidence, and a CAPA process become reports that cannot be defended during an audit.

Direction taken

SafetyOps is the source of truth for incidents and corrective actions. The architecture separates intake, triage, investigation, CAPA, evidence, notifications, and reporting, with critical histories kept append-only.

Business / Product

Problems and solutions

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

Problem

Incidents without owners, evidence, and a CAPA process become reports that cannot be defended during an audit.

Solution

Design a flow from signal to decision, task, evidence, and closure.

Outcome Clear safety workflow
Problem

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

Solution

SafetyOps is the source of truth for incidents and corrective actions. The architecture separates intake, triage, investigation, CAPA, evidence, notifications, and reporting, with critical histories kept append-only.

Outcome Incident lifecycle with auditable state
Problem

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

Solution

Incident lifecycle with auditable state. CAPA and SLA as operating mechanisms.

Outcome Auditable evidence model

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

Critical evidence and decisions carry cryptographic integrity and a custody history, and closing a CAPA or incident requires an authorized role and segregation of duties.

Open competency
Scope
  • Evidence integrity: hashes, metadata, and custody-transfer history
  • RBAC and segregation of duties on CAPA/incident closure
  • Immutable incident timeline, resistant to silent edits
Applied experience
  • Privacy, roles, and auditability built into the product model.
  • Security visible in domain decisions, not only around the UI.
07

AI/ML Engineer

Treating AI as a product capability: with context, constraints, versioned signals, and a clear boundary between facts and interpretation.

Open competency
Scope
  • LLM as a controlled capability
  • Signal and projection quality
  • Responsible product constraints
Applied experience
  • AI constrained by context, signals, and product responsibility.
  • Boundary between facts and interpretation preserved in architecture.

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
DevOps Engineer
  • OpenTelemetry
  • Cloud Logging
  • Kafka operations
Cloud Engineer
  • Object storage
  • Kafka
Security Engineer
  • RBAC
  • Audit log
  • Evidence integrity & custody
.NET / ASP.NET Core Angular web client Event-driven integration Evidence & history domain model OpenTelemetry Kafka operations Kafka Audit log .NET 8 .NET MAUI Evidence integrity (hash & custody) Audit trail .NET MAUI mobile client PostgreSQL Access-control governance Offline-first domain model Cloud Logging Object storage RBAC Evidence integrity & custody Mobile offline sync Angular Append-only incident timeline .NET / ASP.NET Core Angular web client Event-driven integration Evidence & history domain model OpenTelemetry Kafka operations Kafka Audit log .NET 8 .NET MAUI Evidence integrity (hash & custody) Audit trail
.NET MAUI mobile client PostgreSQL Access-control governance Offline-first domain model Cloud Logging Object storage RBAC Evidence integrity & custody Mobile offline sync Angular Append-only incident timeline .NET / ASP.NET Core Angular web client Event-driven integration Evidence & history domain model OpenTelemetry Kafka operations Kafka Audit log .NET 8 .NET MAUI Evidence integrity (hash & custody) Audit trail .NET MAUI mobile client PostgreSQL Access-control governance Offline-first domain model Cloud Logging Object storage RBAC Evidence integrity & custody Mobile offline sync Angular Append-only incident timeline