Developer Edition
Rather run it yourself? Good.
The developer core of Earth Care Network is licensed AGPLv3: the API, the Jaguar runtime, the MCP server, the connectors and the portal. Bring your own model key and pay us nothing for AI. It exists for builders who want to advance the member experience — and for anyone who wants to read the code before trusting it with their business.
The Profit with Purpose skills are public: fork them today. The platform is AGPLv3. Its public mirror is not up yet, so we share the source on request — write to us and a person sends it.
# The skills: public today, fork themgit clone https://github.com/Earth-Care-Network/profit-with-purpose-skills.git # Connect your AI to Earth Care Network (MCP, OAuth)# -> https://www.earthcare.network/mcp/ # The platform: AGPLv3, source on request# -> hello@earthcare.networkWhere the line is
Three layers, stated plainly.
Most of the product is the open core. A thin commercial layer sits under backend/enterprise/. The network itself is not code — it is hosted, and it is the membership.
Open core
AGPLv3Everything outside backend/enterprise/. Fork it, run it, sell services on it — publish your changes if you offer it as a network service.
- Django API + data model
- Directory, CRM, context graph, automation, the billing catalog, metering.
- Jaguar runtime
- The agent loop, tool-calling, the approvals queue, the AG-UI chat.
- MCP server
- Operate the enterprise from Claude, ChatGPT, Grok or your own agent.
- Connectors + App Adapter Kit
- Twenty, Postiz, Murmurations, Stripe — and yours.
- Next.js portal
- The rooms, the public profile, the journal.
Commercial modules
backend/enterprise/Licensed under enterprise/LICENSE_COMMERCIAL rather than AGPLv3. Two rows are marketed today; the rest of the scope named in that licence is roadmap, and is listed here as roadmap.
- White-label agency
- Domain-gated branding for agencies. Not part of the membership, and not available on Community self-host.
- Managed AI tokens
- The hosted convenience: provider cost plus a published margin, paid in tokens. Hosted has no BYOK.
- Roadmap, not shipped
- SSO/SAML, the ad exchange and the data-licensing API are named in the commercial scope. None of them are built. Do not plan on them.
The network, hosted
MembershipNot gated by a licence key, because it is not code. It is the part a fork cannot copy.
- Managed inference
- The estimate before the run, the receipt after it. Amounts live in the product, not on this page.
- Directory, referrals, shared signals
- The aligned context graph across enterprises.
- Ambassadors · 10% lifetime
- Paid when an enterprise you nominate activates, for as long as they stay.
- Earth Care Cloud
- Open-source apps — Twenty, Postiz, Ghost and more — configured and running.
Bring your own key
Self-host plus BYOK means we bill you nothing for AI.
This is the guarantee the open core exists to make credible, not an upsell. Set ECN_DEPLOYMENT_MODE=self_hosted and point the gateway at your own provider keys: every model call runs on your account, and Earth Care Network never bills you for AI. Hosted deployments are the other side of that trade — managed AI at provider cost plus a published margin, and no BYOK.
Metering is in the AGPL tree either way, so the arithmetic behind any number we show you is readable by anyone, on any deployment.
Known limitation, stated up front
The bundled celery-worker service does not receive SECRET_KEY or AI_CREDENTIAL_ENCRYPTION_KEY, so a BYOK credential encrypted by the API cannot be decrypted inside a background task. Set both on the worker to match the API before you rely on BYOK for async work.
The licence boundary is not a clean cut yet
backend/enterprise/is the intended commercial boundary and the rest of the tree is AGPLv3 — but core apps still import it, the project URLconf includes its routes, and the App Adapter Kit's own AppInstallation model still lives there. Deleting that directory does not give you a running deployment. Untangling it is in progress.
Self-host is a build. The membership is plug and play.
Not a scare tactic — just the shape of the work. The Community Edition is the same core, unconfigured: Postgres with pgvector, Redis, Celery workers and beat, object storage, mail delivery, provider keys, migrations and every upgrade are yours to run. On the membership all of that is ours to operate, and every membership funds the builders.
The licence, in plain English
What you may do, and the two things you may not.
A CRM holds your pipeline, your contacts and the AI spend attached to them. You should not have to take that on faith — so read the metering path, confirm what is charged and why, and fork if we ever stop deserving the trust.
- Self-host for your own enterprise, forever, and pay Earth Care Network nothing for AI.
- Read every line that touches your pipeline, your contacts and your AI spend before you trust it.
- Fork and modify the AGPL tree.
- Offer it as a network service — and publish your modifications, as AGPLv3 asks.
- Use the Earth Care Network name or marks to imply an endorsement you do not have.
- White-label Community self-host — agency branding is commercial, and domain-gated.
Contributing
A Developer Certificate of Origin sign-off on each commit — a Signed-off-by line. No CLA is required today. Work on the commercial boundary may need a separate agreement later, so talk to the maintainers before investing heavily there.
Why we recommend the membership even so
The more enterprises grow on the network, the more memberships fund the core; the better the core gets, the more enterprises grow on the network. That is the whole business model, written down so you can hold us to it.
What is not settled here
Dual-licence terms, a contributor licence agreement, the trademark policy for forks and the exact AGPL §13 wording are counsel-gated. This page describes the tree rule and what is marketed today; it is not legal advice.
Start here
Five files, and you will know what we do with your data.
The platform is AGPLv3. Its public mirror is not up yet, so we share the source on request — write to us and a person sends it. Request the platform source
backend/ai/gateway.py- Every model call in the product goes through here. Read it to see what is metered, when a bring-your-own-key credential is used instead of ours, and what is checked before a call is made.
backend/metering/- Usage events and rate cards — the arithmetic behind any number we ever show you.
backend/apps/app_manifest.py- The App Adapter Kit contract: AppManifest, AppAdapter, AppRegistry, and the install → provision → probe → uninstall state machine.
backend/apps/adapters/- Working adapters, not samples: native.py, crm/twenty/, social/postiz.py.
backend/mcp_server/- The MCP surface external agents use. Manifests name their own mcp_tools, so an app is expected to be operable by an agent, not only by a human.
Building an app into the ecosystem
The App Library is an extension point, not a closed shelf. An app is a manifest plus an adapter: AppManifest describes it — slug, version, category, capabilities, credential schema, the route it opens, and mcp_tools, the MCP tools that operate it, because agent-operable is the bar rather than a bonus. AppAdapter implements install, probe and uninstall, and AppRegistry catalogues it. A manifest already carries a billing entitlement, so a paid app is intended — but the publishing and payout path for third-party developers is not built. Build against the kit, and talk to us before you plan revenue on it rather than after.
The more enterprises grow on the network, the better the core gets.
Memberships fund the open core. The open core earns the trust that grows memberships.
The tree rule is written up on the licensing page. Running an agency? White-label is a separate, domain-gated commercial licence — not part of the membership, and not open yet. See licensing and white label.
