About EOTICS
A small engineering company for the hard layers.
EOTICS exists because the most expensive problems in connected products live at the boundaries: where firmware meets the kernel, where the driver meets the bus, where the device meets the cloud. We work across those boundaries so nobody has to hand the problem to another vendor.
Founder-led, hands-on
EOTICS is led by its founder, Ahmed Arif, a systems engineer who works across operating-system kernels, device drivers, firmware and the cloud services that run device fleets. The person who scopes your project is the person who builds it.
Our background is in the low-level work most teams avoid: bringing operating systems up on new ARM64 boards, writing and porting kernel-mode drivers between Linux and Windows, chasing multi-core races and DMA corruption to their root cause, and building the update and telemetry platforms that keep fleets healthy once they ship.
We build on and contribute to open-source operating-system projects, and we document what we learn on the engineering blog. If you want to judge how we think before you talk to us, start there.
Principles
- Reproduce first. No fix is proposed before the failure is reproduced on a rig we can re-run.
- Evidence over opinion. Traces, captures and measurements decide, not seniority.
- Own the boundary. When a bug sits between two layers, we take both.
- Production-grade by default. Error paths, power loss and upgrades are designed in, not bolted on.
- Write it down. Every decision that took more than an hour gets a note the next engineer can read.
How a week with us looks
- Work happens in your repositories and your CI, under your review rules.
- Hardware sits on our bench and yours; when it cannot, we build a QEMU model with a kernel debugger attached.
- One shared channel for questions, one weekly demo on real hardware, one written status note.
- Design decisions and root-cause findings are written as they happen, not reconstructed at the end.
- Handover is scheduled from the start: documentation, tests and a knowledge-transfer session are part of the scope.
What we do not do
- We do not staff projects with junior engineers behind a senior face on the sales call.
- We do not deliver binaries without source, or source without the notes to maintain it.
- We do not accept work we cannot test on real hardware or a faithful model of it.
- We do not guess at root causes. If we cannot reproduce it, we say so and propose how to get there.
- We do not lock you in. Everything we build is designed to be maintained without us.
Core competencies
Embedded
- ARM Cortex-M and Cortex-A targets
- RTOS: FreeRTOS, Zephyr, ThreadX
- Linux kernel and device drivers
- U-Boot, UEFI/EDK2, Arm Trusted Firmware
- Yocto and Buildroot board support
- Secure boot, TrustZone, OP-TEE, TPM
OS & middleware
- Windows kernel-mode drivers (WDM, KMDF, NDIS, StorPort, WDDM)
- SMP bring-up, interrupt controllers, memory ordering
- MQTT, CoAP, gRPC, AMQP stacks
- D-Bus, ZeroMQ, shared-memory IPC
- OTA update agents and orchestration logic
- Compatibility layers: Wine, ReactOS, FEX emulation
Cloud
- AWS IoT Core and Azure IoT Hub
- Kubernetes and containerised microservices
- MQTT brokers and time-series pipelines
- Device provisioning, X.509 and mTLS
- OTA servers and staged rollouts
- Observability, security and compliance for fleets
Ready to work together?
Start with a thirty-minute call. We will tell you honestly whether we are the right team.