Ankior Technologies / SAFETYTECH

EnvControl

An environmental telemetry platform for sensors, gateways, alerts, calibration, violations, and compliance reporting.

DevOps Cloud Security
EnvControl preview
Client: Ankior Technologies Year: 2026

Trust architecture for environmental telemetry

Where the project started

EnvControl never exposes raw telemetry to the client — it aggregates readings into building structure and rules, and every P1/P2 alert requires an authorized role and segregation of duties to close.

Starting point

Sensors alone do not solve the problem if data does not become decisions, tasks, and compliance evidence.

Direction taken

EnvControl separates ingestion, device fleet, calibration, rules, alerts, violations, and reporting. Gateways can buffer data, while the rules domain decides when a signal becomes an operational incident.

Business / Product

Problems and solutions

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

Problem

Sensors alone do not solve the problem if data does not become decisions, tasks, and compliance evidence.

Solution

Design a pipeline from measurement through rule and alert to violation, task, and report.

Outcome Sensor-to-decision pipeline
Problem

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

Solution

EnvControl separates ingestion, device fleet, calibration, rules, alerts, violations, and reporting. Gateways can buffer data, while the rules domain decides when a signal becomes an operational incident.

Outcome Telemetry ingestion with backpressure
Problem

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

Solution

Telemetry ingestion with backpressure. Calibration lifecycle as a domain.

Outcome Model ready for edge gateways

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

Trust in a measurement is an explicit data property (calibration, quality, provenance), and closing critical alerts requires an authorized role plus segregation of duties.

Open competency
Scope
  • Provenance and calibration as an explicit property of every reading
  • RBAC and segregation of duties on P1/P2 alert closure
  • Versioned alert rules traceable to the alerts they generated
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
  • Domain logic engines
  • PostgreSQL
Tech Lead
  • Rules-engine governance
  • Event-driven integration
  • Edge/IoT domain boundaries
  • Access-control governance
DevOps Engineer
  • OpenTelemetry
  • Grafana
  • Cloud Logging
  • Kafka operations
Cloud Engineer
  • Kafka
  • Edge gateway
  • MQTT
Security Engineer
  • RBAC
  • Provenance & calibration
.NET / ASP.NET Core Angular web client PostgreSQL Event-driven integration Access-control governance Grafana Kafka operations Edge gateway RBAC .NET 8 Angular Versioned alert rules .NET MAUI mobile client Domain logic engines Rules-engine governance Edge/IoT domain boundaries OpenTelemetry Cloud Logging Kafka MQTT Provenance & calibration .NET MAUI Calibration & provenance tracking .NET / ASP.NET Core Angular web client PostgreSQL Event-driven integration Access-control governance Grafana Kafka operations Edge gateway RBAC .NET 8 Angular Versioned alert rules
.NET MAUI mobile client Domain logic engines Rules-engine governance Edge/IoT domain boundaries OpenTelemetry Cloud Logging Kafka MQTT Provenance & calibration .NET MAUI Calibration & provenance tracking .NET / ASP.NET Core Angular web client PostgreSQL Event-driven integration Access-control governance Grafana Kafka operations Edge gateway RBAC .NET 8 Angular Versioned alert rules .NET MAUI mobile client Domain logic engines Rules-engine governance Edge/IoT domain boundaries OpenTelemetry Cloud Logging Kafka MQTT Provenance & calibration .NET MAUI Calibration & provenance tracking