Local, fair-code, and Cloud¶

Pisama has four distinct starting points:

1. Open-source SDKs run locally and need no Pisama account.
2. Pisama for n8n self-hosting is fair-code under the Sustainable Use License.
3. Cloud Free adds managed ingestion, storage, and a browser dashboard.
4. Paid Cloud adds capacity and advanced capabilities by plan.

The core pisama and pisama-core Python packages are MIT licensed. Some optional standalone packages use BSL or fair-code licenses, and are labeled individually in their package metadata and repositories.

Pisama for n8n self-hosting is source-available and free for permitted internal use. It is not OSI open source. Its engine, server, dashboard, and deployment files use the fair-code label consistently.

The canonical vocabulary and product allowances are available in the machine-readable capability manifest and the public product comparison.

Public package map¶

Every supported public package has an explicit source, license, and lifecycle boundary:

Package lifecycle¶

• Stable packages are the canonical general-purpose install and engine surfaces.
• Beta packages are supported and tested, but APIs may still evolve before version 1.0.
• Supported integrations target a named host product and follow its compatibility requirements.
• Research packages publish reproducible evaluation methods and evidence. Their schemas may evolve as evaluation practice improves.
• Labs packages are maintained experiments with an explicit source-available license. They are not the canonical local detector engine.
• Maintained implementation packages remain compatible dependencies but are not promoted as separate starting points. Install pisama[auto] instead of choosing pisama-auto directly for new applications.

No published package is currently hard-deprecated or yanked. If a future consolidation removes a public surface, Pisama will first publish a migration path and keep the final compatible release available.

Shared capability boundary¶

This is a shared promise, not forced feature parity. The main local product is SDK, CLI, CI, and MCP oriented. Pisama for n8n self-hosting includes its own server, dashboard, polling, webhook ingestion, and deterministic workflow repairs. Their hosted quotas differ because their storage, model, and operator costs differ.

Feature comparison¶

Hosted plans are currently activated through early access. The open-source SDKs are independent of a hosted plan and continue to work without an account.

What the open-source SDK includes¶

pip install pisama

The local path includes:

• Registered heuristic detectors for loops, corruption, hallucination, coordination failures, and related failure modes
• pisama analyze, pisama watch, and detector inventory commands
• an optional local MCP server with pip install "pisama[mcp]"
• a custom detector API for local extensions
• local deterministic repair primitives from pisama-core
• file, JSON string, Python dictionary, and trace-object inputs
• no required database, Docker service, API key, or Pisama network call

import pisama

result = pisama.analyze("trace.json")
for issue in result.issues:
    print(f"[{issue.type}] {issue.summary}")

Use this path for local development, CI checks, private traces, and custom pipelines that do not need a hosted dashboard.

What Cloud Free adds¶

Cloud Free is the managed starting point. It adds:

• hosted trace ingestion and history
• a browser dashboard for investigation
• core production heuristic detection
• 5,000 ingested events and 10 deterministic healing actions per month
• one project with 7-day retention
• a hosted approval workflow for included deterministic healing actions
• community support

The SDK can continue to run local checks while exporting selected traces to Cloud. Sending traces is explicit configuration.

What paid Cloud adds¶

The paid plans build on Cloud Free:

See the pricing page for current plan allowances and commercial terms.

Self-hosted platform¶

The platform source tree includes a FastAPI backend, Next.js dashboard, PostgreSQL, Redis, and Docker Compose configuration. This is a different deployment surface from the pip install pisama SDK.

Repository access, deployment support, Helm, and air-gapped requirements are handled separately from the public package licenses. Contact Pisama when you need a supported platform deployment in your own environment.

Choose a path¶

Move from local to hosted¶

Moving to Cloud is additive:

1. Keep local pisama.analyze() checks where they help.
2. Configure an exporter or integration for the traces you want hosted.
3. Use the dashboard for shared history, investigation, and managed workflows.

Your local SDK workflow does not need to be removed when you adopt Cloud.