Our product
TraceIT — monitoring that tells you the truth
One console for infrastructure, applications, mobile crashes, user behaviour and alerting. It is built on a rule we hold everywhere in it: a screen never shows a number it did not measure. When something cannot be read, the page says so and says why, instead of showing a zero.
- Delivered, not accepted. Every notification is acknowledged by the device that received it, so the console reports what arrived rather than what was sent.
- Interaction tracking with no markup changes. See which element a person tapped without asking your developers to annotate anything first.
- Crashes and behaviour together. Crash-free users and sessions beside the actions that led to them.
- Your content stays yours. Notification content never passes through a third party.
Analytics
What people actually did: sessions, journeys, and the step where they stopped — each figure traceable to the reading that produced it.
For a school or college groupWhich parts of the parent and student portal get used, where an admission or fee payment loses people, and which campus has gone quiet.
For a hospital or clinic groupWhere a registration or appointment journey stalls, how long a patient spends on each step, and which department’s screens are slowest.
For an IT and platform teamReal traffic, real sessions, a real crash rate — and an honest empty state wherever a reading did not arrive.
System dashboard
A single system on one page: its services, its endpoints, its licences, and what changed since you last looked.
For a school or college groupEvery campus system in one view — the ERP, the LMS, the payment gateway — with whatever needs attention sorted to the top.
For a hospital or clinic groupThe HIS, pharmacy, laboratory interfaces and the integration layer between them, together rather than in four vendor consoles.
For an IT and platform teamServices, endpoints, virtual machines and licence consumption, with the section that failed saying so instead of showing a zero.
Alerts and acknowledgement
What needs attention, who was told, and whether the device they carry confirmed it.
For a school or college groupOn results day, the person on call was told on a phone that confirmed it — not an email that may have been filtered at two in the morning.
For a hospital or clinic groupAn on-call clinician’s handset acknowledged the alert. The console reports what arrived, not what was sent.
For an IT and platform teamDelivery is proven per device, so a missed page is a fact you can point at rather than an argument after the incident.
Executive view
The period in numbers for someone who does not open consoles — availability, incidents, and what was actually fixed.
For a school or college groupA page a trust board or a principal can read without a translator: uptime, incidents, and the work that closed them.
For a hospital or clinic groupThe month as a medical director needs it — availability of the systems clinicians depend on, and where it slipped.
For an IT and platform teamThe figures you take into a review, each one linked back to the reading behind it rather than retyped into a slide.
Dependencies
What depends on what, so an outage has a blast radius you can see before it happens.
For a school or college groupIf the payment gateway goes, you know immediately which campuses and which journeys stop with it.
For a hospital or clinic groupIf the laboratory interface goes, you know which wards will feel it and in what order.
For an IT and platform teamBlast radius before the incident, not reconstructed from memory during it.
Suggested fixes
The specific change that would stop this recurring, ranked, with the evidence that named it.
For a school or college groupA small IT team spends its week on the one change that matters, not on the loudest complaint.
For a hospital or clinic groupThe change that ends a recurring failure, with the measurement that identified it attached.
For an IT and platform teamPrioritised and evidenced — never a generic recommendation you have to go and verify yourself.
These are TraceIT’s own screens. The tenant, the people and the figures are a demonstration — no customer’s data appears here. The product is the same for every sector; what changes is what you read off it.
What it covers
- Infrastructure and applications — hosts, virtual machines, containers, databases and middleware, with dependency and slowest-path views.
- Mobile — Android and iOS crash reporting, crash-free users and sessions, and release health.
- Product analytics — page views, sessions, funnels, and which element a person actually tapped.
- Alerting — to your phone, your inbox and your chat tools, with delivery confirmed per device.
The rules it is built on
- A screen never shows a number it did not measure. If a reading fails, the card says what failed and when. A wrong value is worse than a missing one.
- An absence has a reason. "Never reported" and "reported and cleared" are different facts that need opposite actions, so they never share a rendering.
- Delivered, not accepted. A 2xx from a notification service means it was handed over. TraceIT reports the acknowledgement from the device itself.
- Content stays inside. Where a platform forces a third party into the wake-up path, only a contentless ping travels; the message itself is fetched from TraceIT directly.
Getting data in
An SDK for Android and iOS, a web SDK, and a documented REST ingest contract for anything else. The REST contract works today on any stack, and the native SDKs speak the same contract, so nothing built against it is thrown away.