Question 1

Is this a subscription?

Accepted Answer

No. It is a one-time commercial license, and it includes 12 months of platform updates.

Question 2

Does my license expire?

Accepted Answer

Your license is perpetual for the versions released during your update period. After 12 months, your applications continue to work and your commercial usage rights remain valid. Renew your license only when you want access to newer WorkB2B Platform releases.

Question 3

Can I resell or redistribute WorkB2B Platform?

Accepted Answer

No. You cannot redistribute WorkB2B Platform as a framework, boilerplate, starter kit, template or competing development platform.

Question 4

Can I share the source code with other people?

Accepted Answer

You may not publish or provide the WorkB2B Platform source code to third parties except authorized developers covered by your license.

Question 5

What does WorkB2B Platform actually provide?

Accepted Answer

A multitenant foundation to build your product on. It operates multiple organizations inside one product while maintaining explicit ownership and isolation boundaries; models companies, teams, projects and operational environments without forcing every product into the same hierarchy; defines who can view, create, modify, approve or administer each protected capability; connects authenticated identities with organizations, roles, invitations, sessions and access lifecycle controls; preserves meaningful records of sensitive actions, administrative changes and critical system events; and keeps business modules extensible, so your own product workflows do not require rewriting the platform core.

Question 6

How are tenant isolation and authorization enforced?

Accepted Answer

Through explicit controls instead of assumptions made by individual developers. Protected operations execute within a defined organizational boundary, application-level permissions complement database and infrastructure controls, and missing or invalid context denies a protected operation rather than silently broadening access.

Question 7

Can the platform's security properties be inspected and tested?

Accepted Answer

That is the point of designing them explicitly. The claim is not that security is finished forever, but that your team gets a system where those properties can be inspected, tested and strengthened as the product evolves: versioned migrations keep structural changes reproducible across environments, critical processes can produce verifiable records instead of depending only on transient logs, and important security and architectural rules can be enforced through automated checks and regression tests.

Question 8

Where does the software run, and can my team deploy it?

Accepted Answer

In your own infrastructure. The license includes access to the source code, so your team can run the application using its own accounts, infrastructure and operational policies, and inspect, operate and extend the codebase covered by the agreement. You are not restricted to a hosted page builder or a closed low-code runtime, and the product does not have to depend on a single hosting provider or proprietary execution environment.

Question 9

Who owns the product I build on top of it?

Accepted Answer

You do. Your workflows, integrations, interfaces and vertical capabilities remain part of your product, you deliver the resulting software under your own commercial identity, and your team retains the ability to debug, adapt and evolve the system directly.

Capability	UI templates	Launch-focused boilerplates	Advanced SaaS starter kits	WorkB2B Platform
Primary objective	Provide screens and visual components	Launch an MVP or online product quickly	Provide common SaaS functionality	Build and operate a proprietary B2B product
Typical foundation	Pages, dashboards and components	Authentication, payments, email and database setup	Authentication, billing, teams, roles and admin tools	Multitenant application infrastructure with governed product foundations
Tenant model	Usually not included	Often personal accounts or basic teams	Organizations and team accounts may be included	Organizations, memberships and tenant boundaries treated as core architecture
Authorization	Added by the developer	Usually simple access checks	Roles and permissions are commonly available	Authorization designed as a cross-cutting system for protected product capabilities
Data isolation	Not addressed	Primarily application-level conventions	Depends on the selected kit and implementation	Explicit tenant context and layered isolation designed to reduce cross-tenant access risk
Business structure	Generic interface elements	Generic SaaS account structure	Reusable SaaS modules	Connected B2B foundations for organizations, users, records, workflows, files and operational context
Security model	Left to the implementation team	Focused on common authentication requirements	Includes useful security defaults	Designed around fail-closed behavior, controlled mutations and testable security boundaries
Auditability	Not normally included	Basic logs or third-party integrations	May include activity or administrative tools	Sensitive operations can be designed to produce structured and durable evidence
Operational workflows	Not included	Added when the product requires them	Some jobs, notifications and integrations may be provided	Foundations for durable processing, controlled execution and operational recovery
Architecture governance	No architectural enforcement	Conventions and documentation	Structured modules and established patterns	Automated invariants can protect tenancy, authorization and architectural boundaries
Testing strategy	Component-level at most	Basic tests vary by product	Some products include integration or E2E testing	Critical rules are intended to be verified through regression tests and enforceable gates
Customization model	Replace and assemble components	Modify a reusable starting repository	Extend a general SaaS architecture	Build proprietary workflows and vertical capabilities on top of a maintained core
Update strategy	Occasional template updates	Dependency and feature updates	Product-wide starter-kit updates	Commercial upgrades focused on security, architecture, performance, stability and governance
Long-term responsibility	Entirely assumed by your team	Your team owns the product after launch	Shared between the starter foundation and your implementation	WorkB2B strengthens the common infrastructure while your team owns product differentiation
Best suited for	Marketing sites and interface prototypes	Side projects, experiments and initial MVPs	Conventional SaaS products with standard requirements	B2B SaaS, vertical software, portals and operational platforms with deeper requirements

License	Indie	Team	Business
One-time payment	$199	$399	$899
Developers	1	Up to 5	Up to 10
Own products	1	Up to 3	Up to 5
Commercial use
Source code
Self-hosted
White-label
Tenants	Unlimited	Unlimited	Unlimited
End users	Unlimited	Unlimited	Unlimited
Updates	12 months	12 months	12 months
Security updates	12 months	12 months	12 months
Support	Community / email	Email	Priority email

The multitenant foundation for your own B2B product.

From initial setup to long-term product infrastructure

One license. Your infrastructure. Your product.

Reduce more than development time.

Reduce foundational risk

Avoid the second architecture

Keep your differentiation proprietary

Preserve engineering control

Strengthen the product over time

Scale the engineering organization

One platform. Different B2B products.

Vertical SaaS

Commercial CRM

Client portals

Operations platforms

Partner ecosystems

AI-enabled business software

Three independent paths within the WorkB2B ecosystem.

WorkB2B Community

WorkB2B Platform

WorkB2B Cloud

Platform and license questions

Start with the infrastructure your B2B software already needs.