Treyam · The firm · Bengaluru
We hold ourselves to the same standard we build into a control loop: state what you will guarantee, mark clearly what is only modelled, and publish no number you cannot put a name against.
Treyam is small and recent. We do not have a decade of client logos to show you, and we are not going to borrow anyone else’s. What we have is a handful of engineers who have built and run these systems before, and a way of working we are willing to write down and be judged on.
That is why the rest of this site reads like a datasheet. When a firm is new, the honest move is to get specific — to separate what we commit to from what we have only modelled, and to keep the two visibly apart. A small claim you can check is worth more than a large one you cannot.
We would rather earn the second project than oversell the first. If we are not the right people for the work in front of us, we will tell you early, while it still costs you nothing but the conversation.
The record
We would rather list phases we can defend than dates chosen to flatter us. Where a milestone has not happened yet, it is written here as what comes next, not as what has been done.
At founding
We settled the argument before the service list: one closed loop, six stations, and no handoff between disciplines left unowned. Everything the firm does is arranged around that.
Early on
We wrote the tolerances down — handover, response, rollback, access, change — and published them. They are on this site so that a client can hold us to them rather than take our word.
Now
We build reference models: systems constructed to specification so the architecture can be inspected instead of described. They are labelled as models wherever they appear, and they carry design targets rather than results.
Alongside
We built companies of our own on the same loop: Aegis Foresight, in predictive analytics, and Liv Fresh, whose floating desalination units we invented, built, and still monitor. They are listed below as what they are — Treyam companies — not as client work.
Next
Named engagements, published with the client’s permission and with figures we measured ourselves. Until then this site carries one measured number and no others.
The group
The clearest evidence that we can own a whole loop is that we already do. Each company below lists what Treyam built and which stations of the loop it exercises — and no figure we have not measured.
Predictive analytics
Forecasting and early-warning intelligence for operations, delivered to authorised operators.
Water technology
Drinking water from the sea, powered by the sea: floating desalination units running on wave, solar and wind energy.
The stack
The primitives each stage of the loop names, in loop order — sense, transport, compute, decide, act, verify. If something you need is not on this list, we will say so rather than learn it on your budget.
Tools get replaced. The order of the stations does not, and that is the part we are actually selling.
Tolerances
The same table as everywhere else on this site, because there is only one version of it. Every row is something we would be embarrassed to fail.
| 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 |
hello@treyam.in · Bengaluru, India