S1
Sense
Networking & IT infrastructure
Every signal your operation produces arrives intact, timestamped, and attributable.
SNMP · NetFlow · 802.1X · OpenTelemetry · Zero-trust segmentation
S1 specificationTreyam · Intelligent systems · Bengaluru
We engineer systems that sense, decide, and act.
Networking, cloud, software, machine learning, robotics and the applications that close the loop. Six disciplines, engineered as one system, because the hard part was never any single stage.
06
Disciplines
≤24h
First technical reply
Closed
Loop
01 — The problem
Most operations run open-loop.
Something is measured at one end and something is decided at the other, but nothing carries the result back. The process runs on the assumption that last quarter’s settings are still right.
You can usually tell because nobody can answer a simple question mid-flight: what is this system doing right now, and why did it decide that? The reports arrive on Monday. The decision was made on Wednesday.
A system nobody measures cannot improve. It can only drift.
02 — The model
Close the loop.
The difficulty was never sensing, or computing, or actuating. It is the handoffs between them — and a handoff belongs to whoever owns both sides of it. That is why we cover all six.
03 — The stages
Six stations on one loop.
Not a service menu. Each stage states what it must guarantee — something you could hold us to — rather than what it offers.
S2
Transport
Cloud & platform
Data moves from where it is produced to where it is decided — without loss, and without a surprise invoice.
Terraform · Kubernetes · Kafka · S3 · OpenTelemetry collectors
S2 specificationS3
Compute
Software engineering
The systems that turn signal into state are versioned, tested, and safe to change on a Friday.
TypeScript · Go · Python · PostgreSQL · Trunk-based CI
S3 specificationS4
Decide
AI & machine learning
Every automated decision can be traced back to the inputs that produced it.
PyTorch · ONNX · Vector retrieval · Eval harness · Drift monitors
S4 specificationS5
Act
Robotics & automation
Actuation is bounded: the system has a defined safe state and can always be commanded into it.
ROS 2 · MoveIt · CAN bus · Safety PLC · Fleet orchestration
S5 specificationS6
Verify
Mobile & applications
A human can see what the system did, and disagree with it, from wherever they are.
Swift · Kotlin · React Native · Offline-first sync
S6 specificationSix stages. Six letters. One loop.
04 — How we work
Tolerances, not adjectives.
Every row here is something we would be embarrassed to fail. Nothing on this table is aspirational.
| Parameter | Standard | Method | Evidence |
|---|---|---|---|
| Handover | Reproducible from an empty account | Infrastructure as code + written runbook | Repository |
| Response | First technical reply within 24 hours | Named engineer on rota, not a shared inbox | Ticket log |
| Rollback | Single command, no incident call | Blue/green deploys, backward-compatible schemas | Runbook, deploy history |
| Access | No system depends on one person | Paired operations, documented credentials handover | Access register |
| Change | Nothing merges without a test that would catch its absence | CI gate on every branch | Pipeline history |
05 — Reference models
The loop, applied.
Calibration notice
These are reference models — systems built to specification to demonstrate the architecture we apply. They are not named client engagements, and the figures shown are engineering targets, not measured outcomes. We publish no performance figure we cannot put a name against.
Throughout this site, solid rules mark measured values and dashed rules mark modelled ones.
MeasuredModelled
REF-01 · Model
Robotics & automation
Autonomous warehouse fleet
Representative system. Not a named client engagement.
- Target
- Path conflicts resolved at fleet level, not per unit
- Method
- ROS 2 orchestration, shared occupancy map, central arbiter
- Scope
- Multi-aisle facility, mixed-payload mobile units, design target 50+
- Outcome
- Collision avoidance moves from each robot negotiating locally to one planner holding the whole floor
REF-02 · Model
Machine learning & networking
Urban intersection sensing
Representative system. Not a named client engagement.
- Target
- Inference at the pole, not in the datacentre
- Method
- Edge vision models, batched telemetry, store-and-forward uplink
- Scope
- Signalised intersections with intermittent backhaul
- Outcome
- Decisions survive a network outage because the deciding stage sits on the same pole as the sensing one
REF-03 · Model
Cloud & platform
Zero-downtime platform migration
Representative system. Not a named client engagement.
- Target
- Cutover reversible at every step
- Method
- Dual-write, shadow reads, blue/green cutover, single-command rollback
- Scope
- Stateful services with a live transactional workload
- Outcome
- Migration becomes a sequence of reversible steps rather than one irreversible weekend
06 — Treyam companies
The loop, run for real.
The models above were built to show an architecture. These are companies we built and still operate — the same six stations, carrying a live load. Solid rules: they exist, and you can visit them.
TC-01 · Treyam company
Predictive analytics
Aegis Foresight
Forecasting and early-warning intelligence for operations, delivered to authorised operators.
- Built
- The forecasting models and the operator console that puts their output in front of the people who act on it.
- Status
- Operator platform · restricted access
TC-02 · Treyam company
Water technology
Liv Fresh
Drinking water from the sea, powered by the sea: floating desalination units running on wave, solar and wind energy.
- Built
- The device and the concept, invented, designed and built in-house — and the loop that runs it: on-unit sensing, the uplink from sea to shore, and the dashboards the units are monitored from.
- Status
- Units in the water · monitored by Treyam
≤24h
First technical response
The reference models above are modelled. This is measured.
Bring us the part of your system you cannot see.
Start with the measurement problem. The automation follows from it, and it is a great deal cheaper once the loop is closed.
hello@treyam.in · Bengaluru, India