Caffeine has expanded its business offering with the addition of single sign-on (SSO), giving organisations a simpler way to manage access while strengthening the collaboration tools introduced with its recently launched Business Plan.
The latest update allows teams to sign in to Caffeine using the same authentication system they already use across their workplace. Instead of creating and managing another password, employees can log in through their company’s existing identity provider, reducing friction while helping businesses maintain established security practices.
The SSO feature arrives as part of Caffeine’s Business Plan, which is aimed at organisations building applications collaboratively. The plan combines shared workspaces, team management tools, role-based permissions and administrative controls into a single environment where multiple people can create, edit and publish applications together.
During a walkthrough of the new features, Caffeine’s Ilas explained that the Business Plan builds on the capabilities already available through the Studio plan while introducing features designed for larger teams.
Subscribers receive ten times the credits offered in the Studio plan, alongside access to email services for users, application insights, custom domains and publishing through the Caffeine App Marketplace. Those features are joined by shared workspaces, administrative controls, team collaboration tools, priority support and seats for up to five users as part of the standard subscription.
The shared workspace sits at the centre of the new experience. Rather than keeping projects tied to an individual’s account, organisations can create dedicated workspaces where applications belong to the wider team.
Users can switch between their personal workspace and any team workspace through a simple menu without affecting projects stored in either location. Personal applications remain separate while shared projects become accessible to authorised colleagues.
That structure allows businesses to organise development across departments while giving employees visibility over applications relevant to their work.
Demonstrations showed a company workspace containing a range of internally developed tools, including a blog, messaging platform, expense tracker, HR application and delivery management system. Each application could be opened, edited and shared with colleagues directly from within the workspace.
Collaboration extends beyond simply granting access.
Team members can invite colleagues into individual applications with different permission levels. Someone joining as a commenter, for example, can review an application, leave feedback and take part in discussions without changing the underlying project.
Comments become part of the application’s activity feed, allowing developers to respond directly before sending requests to Caffeine’s AI builder.
During the demonstration, a collaborator highlighted incorrect date information within an application. Rather than manually rebuilding the affected section, the developer selected the discussion and submitted the issue to the AI builder, which automatically queued the task for correction.
This workflow keeps conversations connected to development while reducing the need to move between communication platforms and coding environments.
Managing larger teams has also become a central focus of the Business Plan.
Administrators can invite colleagues through an email invitation, assign them to the organisation and monitor overall usage from a central dashboard.
The management interface provides visibility over available seats, current team members and remaining credits. Businesses can begin with the five included seats before expanding as their organisation grows.
Additional members can be added beyond the initial allocation, with pricing displayed before changes take effect.
Role management introduces another layer of control.
Administrators have unrestricted access to organisational functions, including billing, domain purchases, publishing applications to the marketplace, assigning ownership of projects and monitoring overall credit usage.
Standard users receive access focused on application development while remaining unable to perform administrative actions that may incur additional costs or alter organisational settings.
Businesses can also promote users to administrator status whenever required, allowing responsibilities to shift as teams evolve.
Seat types add another level of flexibility.
Instead of giving every employee unrestricted access to the shared credit pool, administrators can define usage limits for individual team members.
Basic seats provide modest access to credits, making them suitable for lighter workloads or occasional contributors.
Standard seats offer broader access, while unlimited seats remove spending restrictions entirely, allowing heavy users to build extensively without individual limits.
This approach gives organisations another way to manage resources while supporting different styles of work across departments.
Billing controls have likewise been expanded.
Businesses can view their subscription status, manage monthly or annual billing, monitor available credits and purchase additional capacity whenever needed.
Annual subscriptions include savings compared with monthly billing, while organisations remain free to switch between billing cycles if their requirements change.
Should a team consume its available credits more quickly than expected, administrators can manually purchase additional credits or enable automatic top-ups.
Automatic top-ups allow organisations to nominate a minimum credit threshold. Once usage falls below that level, additional credits are purchased automatically, helping prevent interruptions during active development.
Application management has also received considerable attention.
Within the shared workspace, administrators can see every application owned by the organisation, including publication status, ownership details, collaborators and recent activity.
Perhaps one of the most practical additions is the ability to transfer ownership of applications between team members.
Projects no longer remain permanently attached to the developer who created them.
Instead, administrators can reassign responsibility as applications mature or move between departments.
A developer may build an internal HR application before handing ownership to the human resources team, which can then oversee updates, monitor user feedback and continue improving the software over time.
The feature also helps organisations avoid duplicated work by giving teams visibility across existing applications while clarifying ownership responsibilities.
Custom domains remain available through the Business Plan, allowing organisations to connect branded web addresses to their applications.
Administrators can browse available domains directly within Caffeine, purchase them using credits and assign them immediately or at a later stage.
Access to domain purchasing is deliberately limited to administrators, reducing the likelihood of unintended spending.
The same restrictions apply to publishing applications through the Caffeine App Marketplace.
While standard users can view marketplace information, only administrators can publish applications or modify an organisation’s marketplace profile.
Those permission controls are intended to give businesses confidence that public-facing changes remain under appropriate oversight.
The newest addition, single sign-on, strengthens those management capabilities by simplifying authentication.
After configuring an organisation’s preferred identity provider and verifying its domain, employees can access Caffeine using their existing company credentials.
Instead of remembering another password, users enter their company email address and authenticate through the systems already used across the organisation.
The approach mirrors the experience many employees already encounter when accessing workplace software, helping reduce password fatigue while supporting existing identity management practices.
For businesses already using central authentication systems, introducing Caffeine into daily workflows becomes considerably simpler.
Ilas described the feature as a natural extension of the Business Plan, allowing organisations to bring employees into a shared account through familiar onboarding processes before collaborating within common workspaces.
As teams continue building applications together, the combination of shared workspaces, administrative oversight, project reassignment, collaboration tools and simplified authentication aims to provide a single environment where development and management happen side by side.
Caffeine’s Business Plan reflects a growing emphasis on collaborative application development rather than individual projects. With shared ownership, flexible permissions, integrated AI assistance and now single sign-on, the platform is positioning itself as a workspace where organisations can build, manage and publish applications using processes that fit comfortably into existing business operations.
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life
Community Discussion