Skip to content
Cadencor

company

Cadencor is the company. Pulse is the platform.

Cadencor builds software for physical businesses: the stores, restaurants, clinics and depots that run on machines standing in rooms. Pulse is the platform family all of it belongs to, and every Pulse product is usable on its own.

the name

Cadence, core systems, continuous operation

Cadencor joins cadence, a steady beat you can rely on, to core — the system underneath it. It is the company and the promise: the rhythm of a business that does not stop because something upstream wobbled.

Pulse is the platform family. The beat is the metaphor both names share: the signal that says a location is alive and trading.

what we are not

Honest about the field we are in

Mature point of sale systems have had substantial local and offline architecture for years, and we are not going to claim otherwise. We do not sell “the only POS that works offline.”

What we sell is the combination: cloud operations, an endpoint agent that understands location topology, a local runtime and an offline-first register in one platform — sitting alongside the systems already installed, or replacing them when it earns it.

See the product line

What we optimise for

  1. Local is the default, not the fallback

    A site should behave the same whether the network is up, slow or gone. Anything that only works online is a degraded version of the product, so the local path is designed first and the cloud path second.

  2. The cloud is a participant, not a dependency

    Cloud services carry configuration, identity, reporting and orchestration. They stay off the critical path of a transaction. If a site cannot reach us, the site is still a first-class system.

  3. Resilience belongs to the data, not the process

    Durable local state, explicit synchronisation and defined authority rules between the cloud and the site. We would rather spend complexity on replay and reconciliation than on pretending a queue is enough.

  4. Adopt in pieces, or not at all

    No product in the family requires another. An operator can take the agent, the operations layer or the edge runtime without touching the register, and that is a promise about our business model as much as our architecture.

  5. Know the location, not just the hostname

    The value of fleet management in a physical business comes from understanding what each machine is, who depends on it and what stops when it fails. Topology is data we refuse to throw away.

  6. Boring where it counts

    Typed contracts, clear module boundaries and few dependencies in the trust path. Novelty is a cost we only pay when a requirement demands it.

What the architecture guarantees

99.999% is a design target for the store-side path, not a published SLA

store-side availability target
99.999%
offline window
unbounded
critical-path cloud calls per sale
zero
products required to buy another
none
next

Want to see it hold up under a bad day?

Bring your topology and your outage history. We will show you what survives it.

Talk to salesBack to the top