Access
Accounts and permissions, across your products.
Use passkey-first sign-in and manage workspace membership and product-level permissions without creating a separate account experience for each app.
For teams shipping multiple products
One platform behind every product you ship.
Bring accounts, product access, and user issues together across your product portfolio. Spend less effort rebuilding the same operational tools for every app.
Accounts & permissions · Plans & licenses · Reports & replies
Example Studio 4 products · 1 open issue
- Editor Web Healthy
- Editor Desktop Healthy
- Archive Service Pending verification
Export did not complete.
Reported from Editor Web · current release
Example data. Not a live workspace and not customer activity.
01
Your next product should not mean another back office.
A new app needs more than its core features. Someone still has to manage accounts, check product access, and respond when something goes wrong.
Build the product-specific experience. Reuse the operational foundation.
Separate products.
- Product AAccounts · Licences · Inbox
- Product BAccounts · Licences · Inbox
- Product CAccounts · Licences · Inbox
Every product rebuilds accounts, permissions, licensing and a support inbox.
Connected operations.
- Product AProduct features
- Product BProduct features
- Product CProduct features
Access · Commerce · Care
Product-specific features and data stay in the product. The shared operational layer is reused.
02
From “I can't export” to an answer with context.
-
Identify the product
See where the request came from and which release is involved.
-
Check the right access
For a verified user, review the relevant product permissions and entitlements within your authorized scope.
-
Understand the issue
Bring the user's description and available technical evidence into the same case.
-
Respond or hand off
Reply in context, or prepare the evidence your developer needs to investigate.
One case. Less back-and-forth between tools.
- Verified reporter
- •••
- Editor Web
- ISS-0001
- Current release
- 3.1.7
- Report received
- 11:42
Example data. Not a live workspace and not customer activity.
03
Three connected areas. One working context.
Commerce
Connect purchase records to product access.
Organize plans, licenses, seats, and usage entitlements around the products your customers use. Keep payment processing separate from the access decisions inside your product.
Care
Reports that stay connected to the conversation.
Bring user reports, relevant diagnostics, and replies into a shared support workflow. Give your team the context to investigate and your users a way to follow up.
Choose the modules that fit your setup.
04
Built for teams with more than one product to run.
A web app and its desktop companion. Several SaaS products. A small studio shipping a growing collection of tools.
Keep product identity and operating context together, while each app keeps the experience that makes it useful.
- For small product teams.
- For software studios.
- For web and desktop portfolios.
05
Start with one product. Add what you need.
-
Choose the operational problem to solve.
Start with accounts, product access, or user issues.
-
Connect the relevant product.
Use the supported integration path for your application and environment.
-
Keep the workflow together.
Give your team a consistent place to manage the connected work.
Already have an identity or payment provider? Let's map the integration around the systems you use.
06
Shared operations. Clear boundaries.
Keep workspaces and product permissions distinct. Give team members access to the work they are responsible for, and keep customer-facing replies separate from internal notes.
Collect relevant issue context rather than asking users to send everything. Keep the product-specific data and logic that belong in your application there.
07
A few practical questions.
Do we have to replace our existing authentication or payments?
Not necessarily. Start with the modules that fit your needs and review the supported integration path for your current stack.
Is this only for websites?
The platform is intended for teams with web and app products. Confirm the reporting and integration options for the runtimes you use.
Does IO Patina answer our users' support requests for us?
Your team manages your users' reports and conversations. IO Patina provides the platform and support for the platform itself.
Does Platform replace our application's backend?
No. Your application's core features, product data, and business rules stay with your product. Platform connects the shared operational work.
Can we start with one product or one module?
Yes, within a supported configuration. We can review the products, modules, and integration work involved in your setup.
How do we discuss pricing and fit?
Tell us about your products and the workflows you want to connect. We will discuss the scope and commercial terms with you.
08
Bring the next product into the same operating picture.
Tell us what you are building, what you already use, and where operations are becoming repetitive.
Already using Platform? Sign in.