Use cases
Connect, negotiate, complete is the spine behind the first three of these. Buying something and asking about your own money run on your phone instead, through the vault and the on-device engine rather than through a connection. One of the five is an honest no, three more are narrower than they sound, and the badge says so before the sentence beside it does.
The flagship. An employer declares what payroll needs and you approve the set once.
The protocol underneath runs in production. There is no payroll ask in the product yet, and your AI has no way to hand back just the gaps it could not fill.
The same shape with the direction flipped: you send the client a link.
Only a business holding a key we installed can open a session, so an individual cannot start one. This is a no, not a soon.
Point a tool at the accounts you already run, by name rather than by credential.
The shape the protocol was designed and tested against. ShareLess passes on an approved list of names; it never obtains the access itself, and it holds no key.
Your agent starts it, and you authorize the exact final amount with one hold on your phone.
Real and narrow, and it is two lanes. Most stores fill on your phone; a Shopify store runs in our cloud runner, where the card is sealed to that runner rather than staying on your device.
Ask what you spend and get an answer computed on your iPhone from your own files.
The strongest thing on this list. The tradeoff is that you import statements yourself; there is no bank connection.
Each page splits its use case into several claims with a badge apiece, so a badge on a row here is one rung out of that page's set, picked as the fairest summary. It is never a rung the page does not use. The flagship is the one to check first: this row says Limited path, and the page opens with Not covered today.
Enforced today means a ShareLess path holds the value or pauses the action. Available now means it runs in production for whoever can reach it. Limited path means it is real but narrower than the sentence beside it sounds. Coming next means built far enough to describe, not far enough to use. Not covered today means no path exists and none is close. Designed, not built means a decision we have made with no runtime code behind it.