About us

We build the software that industries run on — and then we run it.

Xentinel Labs is a product company that also takes on engineering work. That order matters. Everything we know about building for someone else, we learned from having to live with our own decisions in production.

Our story

It started with an exporter and a folder called “FINAL_v7”

We were asked to build a dashboard. Two weeks into mapping the workflow it was obvious the dashboard was not the problem — the export desk was running on eleven disconnected systems, and the numbers on any given screen were already three days old.

So we built the system underneath instead. That became Xenfloo. The same pattern repeated in healthcare, where credential expiry was being tracked by whoever happened to remember, and on the hardware side, where a facility only discovered an empty tank when the taps ran dry.

Today we run three product lines and an engineering practice, and the two feed each other. Client work exposes problems worth productising; running our own products keeps the engineering practice honest about what maintenance actually costs.

What we do, in one list

  • Xenfloo — agri-export operations SaaS
  • StayCred — healthcare credentialing platform
  • Connected hardware — sensing and access devices
  • Custom application development
  • Web and mobile product engineering
  • Data platforms and analytics
  • AR, VR and XR applications
  • IoT, firmware and fleet operations
Talk to the team
How we think

Five things we will not compromise on

Not values on a wall — the actual arguments we have internally, settled.

Own the outcome

A feature that ships and nobody uses is a failure, however clean the code. We measure ourselves on whether the workflow got better.

Boring where it counts

Proven databases, obvious architectures, few dependencies. Save the novelty for the part of the product that is genuinely novel.

No black boxes

Live staging, an open backlog, a demo every cycle and your repository from commit one. If you cannot see it, we are doing it wrong.

Say the hard thing early

We would rather lose a project at the brief than deliver something we knew would not hold. Half our discovery work ends in a smaller scope.

Design and engineering together

Interface, data model and workflow get designed in the same room. Hand-offs are where products lose their coherence.

Leave them able to leave

Documentation, training and an exit plan are part of delivery. A client who stays because they are trapped is not a reference.

How we work

A rhythm you can plan your own quarter around

Every engagement runs on the same cadence, whether it is a six-week fixed-scope build or a two-year managed product.

Week 0 — Brief

A conversation with an engineer, not an account manager. You leave knowing whether we are a fit.

Weeks 1–3 — Discovery

Workflow mapping with the people doing the work, a written architecture and a scoped number.

Fortnightly — Delivery

A demo, an updated staging environment and a re-orderable backlog. No status reports nobody reads.

Go-live and beyond

Security review, load check, runbook, training — then an SLA or a clean handover.

Capabilities in-house

One roof, nine disciplines

Nothing critical gets subcontracted to a stranger halfway through your project.

Product design Frontend Backend Mobile Data engineering Firmware XR / 3D DevOps QA
3
product lines in production
2 wk
delivery cycle, every engagement
Careers

We hire people who want to see their work in production

Small teams, real ownership, and products with actual users on the other side. If you like shipping and dislike ceremony, we are probably a good place to work.

  • You own features end to end, from problem to production
  • Time set aside for the platform work that is never urgent
  • Hardware, XR, data and product engineering under one roof
  • No layers between you and the person using what you built

We read everything sent to ai@xentinellabs.com. A link to something you built beats a formatted CV.

Product engineers

TypeScript, React/Next.js, Node or Python. You care about the data model as much as the interface.

Firmware & IoT engineers

Embedded C, low-power design, LoRa/BLE/cellular. Comfortable with an oscilloscope and a debugger.

XR developers

Unity or Unreal, WebXR, 3D pipelines. Interested in training and industrial use cases, not gimmicks.

Currently taking briefs for Q4

Tell us the workflow. We’ll show you the build.

Thirty minutes with an engineer who has shipped this before — not a sales call. You leave with a scoped approach, a rough timeline and an honest answer on whether we’re the right team for it.