Your listing
App description, screenshots, categories and versions. Each submission goes through review, and both approval and rejection are recorded.
Service providers
Build a service on the operator’s own data
Analytics, marketing, guest engagement, staffing, accounting. Your product is not a till and not a kitchen screen — it is the layer that makes sense of what they produce. SIDES is where that data already lives.
The fit
Distribution and data in the same step
A service business selling into hospitality usually fights two problems at once: finding the operators, and then getting clean, current data out of whatever they run. The marketplace answers the first. The API answers the second, and answers it the same way for every customer you win.
An operator finds your listing inside the product they already use and reads what it does. What is settled today is the contract you build against: one documented API, versioned, with one error shape — rather than a per-customer export pipeline you rebuild for every win.
The part your customers will ask about
What your customers will ask, and what the answers are
You will be asked this in every procurement conversation. The answers are the same for every partner, which makes them easy to give.
- Your client’s reach is its scopes
- Scopes govern what your partner client may do on SIDES LABS. They are hierarchical, granted to your client by SIDES, and enforced server-side on every single request — so what your integration can touch is a property of the platform, not of an agreement.
- Consent is recorded
- Every consent SIDES LABS records is stored with its document version and its timestamp, so “when did they agree, and to what” has an answer rather than an estimate.
- Deletion is anonymisation
- A departing person disappears from the data while the audit trail and the published marketplace history survive. That is a GDPR design decision, taken once, for everyone.
- No third-party requests
- Nothing on this platform loads from a CDN, a font host or an analytics beacon. An IP address is personal data; we do not hand yours or your customers’ to anyone.
- Partner isolation
- Another partner cannot see your apps, your statistics, your revenue or your team. Every partner-scoped query is filtered by the authenticated principal, server-side.
- Nothing publishes itself
- Listings, reviews and editorial reach a SIDES customer only through an explicit, recorded state transition. Your listing does not change because something else did.
Running the business
What the partner area gives you
Ratings and reviews
What operators say about the service, with their moderation state always explicit. Nothing is silently editorialised in either direction.
Usage statistics
How many SIDES customers actually use your service. Which SIDES API supplies them, and at what granularity, is still being decided — what is settled is that they come from the platform and not from your own instrumentation.
Tier, billing and team
Your subscription and its entitlements, your invoices, and your colleagues — each with the role they need: administrator, developer or accounting.
Will I have to handle my customers’ SIDES credentials?
No, and you should never ask for them. Your integration authenticates as your own OAuth 2.0 client, with the scopes SIDES granted it. Anything the marketplace adds beyond that will be in the API changelog before it is in a screen.
What decides what my subscription can do?
The subscription row on our side, checked in the service layer on every write path. Never the payment provider, and never a hidden button in a screen — a gate that exists only in a user interface does not exist.
Can I try before I list?
Yes. A registered partner can build and submit without being published; a listing only becomes public when SIDES approves it.
What exists today
The platform is being built in the open, and this page describes the platform being built. Today the API authenticates OAuth machine clients and reports the identity, scopes and rate limit of the calling principal. Partner registration and sign-in, the marketplace catalogue, the API changelog, the developer resources, usage statistics and the tier pages come in the phases after it — every commitment above is a commitment, not a screenshot.
Reach the operators — they already have the data
Registration creates your business partner, your first administrator and your tier. Publishing is a separate, recorded step.
