Ankior Technologies / SAFETYTECH
SmartAid
A platform for smart first-aid kits, AEDs, and aid points, monitoring readiness, usage, shortages, and replenishment.
First-aid readiness under operational control
Where the project started
SmartAid turns first-aid kits and AEDs from passive equipment into a managed readiness network: indoor and outdoor kits get separate access models, and field operations run offline with deduplication and replayable history.
SmartAid connects device readiness, kit inventory, AED context, usage sessions, restocking, and supply operations. The architecture must work in the field, so it assumes offline capture, deduplication, and later evidence reconstruction.
Business / Product
Problems and solutions
Each tile connects a real product tension with the decision that clarified the domain, UX, or operations.
A first-aid point can appear ready, but without usage, shortage, and replenishment history the organization is guessing.
Design a readiness model for kits, usage sessions, supply, and edge operations.
The scope could easily become a feature list without one product, data, and ownership model.
SmartAid connects device readiness, kit inventory, AED context, usage sessions, restocking, and supply operations. The architecture must work in the field, so it assumes offline capture, deduplication, and later evidence reconstruction.
The project needed decisions that would stay readable after the first version: for users, the team, and further delivery.
Readiness score for aid points. Usage sessions as operational evidence.
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
Field operations run offline with deduplication and data integrity, and emergency override for public AED access stays visible and auditable instead of hidden.
Open competency- Offline-first capture with deduplication and replayable history
- Emergency override for AED access stays visible and auditable
- Service-book history as proof of rescue-equipment readiness
- 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
- Edge/IoT domain boundaries
- Offline-first domain model
- OpenTelemetry
- Cloud Logging
- Kafka operations
- Kafka
- Edge gateway
- Audit log
- Auditable emergency override
Product preview
Gallery
Selected screens and materials showing the product surface, UX decisions, and work outcome.