7.3 Editions and distribution options
Teloa has three editions: Community (formerly Free), Pro and Enterprise. The current stable Community release is 0.2.2 on GitHub Releases and Docker Hub; npm provides the same native release. Pro and Enterprise are not available for purchase or immediate use. Cloud is not a separate edition; independent cloud execution is a planned direction for Enterprise.
| Edition | For whom | Access and main value | Current status |
|---|---|---|---|
| Community | Individuals and one-person companies (OPCs) who deploy it themselves | Open-source Web, the complete available personal workflow, code control and self-managed maintenance; no Teloa cloud account required | Stable 0.2.2; GitHub Releases, Docker Hub and source are available; npm is available |
| Pro | Professionals and OPCs who use Teloa frequently | Native Mac workbench, local execution and integrations; create work, follow progress, handle approvals and access results remotely from a phone | Planned |
| Enterprise | Organizations with multiple human users and governance requirements | Enterprise identity, organizational permissions, shared resources, audits and deployment in customer-controlled environments | Planned, subject to actual delivery scope |
Shared core and cost boundaries
Community keeps its complete available personal workflow; existing capabilities are not withdrawn when commercial editions are added. Pro adds native clients, local integrations and remote mobile access on the shared core. Enterprise adds governance and delivery support. npm and Docker are Community installation channels, rather than additional paid editions. See Install and run.
You configure your own model services and pay their usage costs in every edition. A Pro subscription provides software access. Local tasks run on your own Mac, without independent cloud compute. Enterprise licensing, deployment resources and delivery services are agreed separately. Prices have not been announced.
Pro: Mac execution with remote mobile access
Pro plans to use the same account, Mac execution host and conversations. Start work directly on your Mac, or create work, follow progress, add materials, handle approvals and access results from your phone after pairing and authorization.
| Interface or service | Responsibilities and boundaries |
|---|---|
| Mac client | Enter requests, run work, handle approvals and access results directly, without selecting your own device or assigning work back to your own Mac |
| Mobile client | Remotely use your authorized Mac and the same conversations; the Mac must be online with its execution host running |
| Public Web | Registration, sign-in, account recovery and returning to the client; no Pro task workbench |
| Cloud services | Accounts, licensing, device connections and explicitly authorized data transfer; no independent task execution |
| An offline Mac | Wait for the original device and preserve task state; no automatic cloud reassignment or repeated execution |
An activated local engine can operate independently during its valid licence period. A temporary account service outage should not interrupt local tasks already running. Offline licence periods and renewal rules will be published before availability. Local execution does not imply offline models; remote models still need a network connection.
Mobile reuses the Mac Harness, conversations and results. Supported platforms and remote operations follow actual release documentation. Mac is the current priority; mobile is not available yet. See Pro and the direction for independent cloud execution.
Signing in and pairing do not upload all local materials automatically. Storage locations, transfer scope, execution permissions and approvals are confirmed separately.
Enterprise boundaries
Enterprise supports organizational governance and customer-controlled environments. It can use enterprise identity and licensing without requiring the public Pro account service to remain online. Multiple human users, SSO, organizational audits, security gateways, multiple engines and distributed execution follow development and actual delivery scope. Independent cloud execution is still under evaluation; it does not imply an available hosted service. See Enterprise.
Actual operation remains subject to model quotas, compute resources, technical validation and security boundaries.