About

Built for one trade, on purpose.

Most retail software treats a ring as a product with a quantity. We started from the opposite end: a single piece, with a serial, a weight, a stone and a cost that moves with the metal market.

Why we exist

Generic POS was never built for a piece that exists once.

Jewelers have spent years bending generic point-of-sale systems into shape. Each workaround is reasonable. Together they are a job nobody was hired to do.

  • A custom field for karat
  • A spreadsheet for repairs
  • A second spreadsheet for memo
  • A monthly reconciliation

Those workarounds are not a software problem, they are a modelling problem. If the system understands that a piece is unique, that customer-owned goods are not your stock, and that today’s gold price changes your real margin, most of them simply stop being necessary.

How we work
We would rather say “not yet” than ship a half-feature.
Where something is undecided — module trials, retention periods, response targets — this site says so instead of guessing. It is also how we intend to answer questions on a sales call.
What we hold to

Three commitments, and no mission statement.

Your data is yours

Export your stock, customers and transaction history whenever you like, in a format something else can read. A system you cannot leave is not a system you chose.

One core, priced honestly

Capability arrives as modules you can decline. Adding a module never reprices what you already run, and nothing is bundled to inflate a tier.

Cloud or your own server

On-premise is a supported deployment, not a reluctant exception — because data residency and a bad rural connection are real constraints, not edge cases.

Company details pending. Team, location, founding story and any customer references are placeholders in this design phase.

The best way to judge it is to use it.

Fourteen days on your own stock will tell you more than anything on this page.