Community

Contribute. Connect. Use it well.

Powerloom Home is open under ELv2. Contributions welcome. The maintainer is small (one human, one AI), so here's how to make contributions land smoothly.

Where to go

Issues — bug reports, feature requests, MCP template suggestions. github.com/shanerlevy-debug/powerloom-home/issues
Discussions — questions, ideas, show-and-tell. github.com/shanerlevy-debug/powerloom-home/discussions
Pull requests — code + doc contributions. File an issue first for anything non-trivial so we can agree on direction before you invest time.
Security disclosures — email directly rather than public issue: security@powerloom.tech.

What's in scope for home

Good targets for contribution:

New MCP templates — container images + handler implementations for the 10 SaaS integrations not yet shipping (github, notion, jira, linear, google_drive, etc.). See the templates page for the full list.
New runtime drivers — first-class support for local models (Ollama, LM Studio), open-source model providers, and multi-model routing.
Handler improvements — richer tool surfaces for files, postgres, slack. More policy constraint options.
Operator tooling — extensions to scratch/home_init.py, better error recovery, better logs.
Documentation — tutorials, cookbook recipes, integration walkthroughs with other tools.
Bug fixes — obviously.

What's not in scope for home

Some things are intentionally enterprise-only. If your idea falls here, file an issue tagged enterprise-only — we'll consider it for powerloom.tech.

Multi-tenant RBAC. Home is single-user by design. Multi-user governance lives in the enterprise edition.
Billing + tiers + Stripe. Home is free; the SaaS monetization infrastructure stays out.
Super-admin console. The compiled-out super-admin surface is enterprise-only.
Production AWS Terraform. Home uses the docker-local MCP spawner; the Terraform-based fleet is enterprise.
SaaS-backed features that require an always-on operator team (SLA-backed support, hosted PII storage, managed audit exports).

Contributing workflow

File an issue. Describe what you want to do + why. Small bug fixes can skip this step.
Fork + branch. Branch from main, one topic per PR.
Write tests. New code needs tests. Mirror the existing patterns in api/tests/.
Pass the test suite. docker compose exec api pytest should be green.
Open the PR. Reference the issue. Describe what changed + why.
Respond to review. Iterate on the same branch; maintainer squash-merges when ready.

Full details: CONTRIBUTING.md on GitHub.

Tone + voice

User-facing copy (docs, error messages, UI text) follows the brand voice: brand_docs/brand_voice.md. Direct, competent, restrained. No emojis, no "Great question!", no marketing fluff. Flat statements of fact.

Code comments, commit messages, and issue responses: same vibe. Precise, no hedging. If you're not sure, copy the existing style.

Need the enterprise edition?

If Powerloom Home isn't enough for your use case — multiple users, audit compliance, managed infrastructure, SLA support — the enterprise SaaS lives at powerloom.tech.

Some enterprise features flow back to home over time as they prove out. Some stay enterprise-only by design (billing, multi-tenant governance). Roadmap visibility: home roadmap + enterprise roadmap.