OpenSecret

license

MIT(Maple-client)+AGPL-3.0(OpenSecret-platform),both-OSI

source

public(github.com/OpenSecretCloud)

core features withheld

no — billing and feature-flag APIs are optional and external

models

open-weight

hosted-tier

paid(managed-enclaves)

Maple AI's two components are each open under an OSI license: the client under MIT, and the OpenSecret confidential-computing backend under AGPL-3.0, serving open-weight models. The paid tier buys only hosted use of managed enclaves; a self-hosted backend runs without billing or feature-flag services, and neither repository has an enterprise directory or license key gating the source.

• https://github.com/OpenSecretCloud/Maple recorded 2026-06-17

  MIT-licensed Maple client (Tauri/Rust/TS), active; multi-platform

• https://github.com/OpenSecretCloud/Maple/blob/master/LICENSE recorded 2026-08-12

  the Maple client repository LICENSE is a plain MIT License; the GitHub repo API reports the SPDX id MIT

• https://github.com/OpenSecretCloud/Maple/blob/master/README.md recorded 2026-08-12

  the configuration surface lists VITE_OS_FLAGS_BASE_URL as "an optional feature-flags API" and VITE_MAPLE_BILLING_API_URL as "an optional billing API", and states "Flags and billing are independent clients"; the quick start runs the client against a local OpenSecret backend at 127.0.0.1:3000 with no paid component

• https://github.com/OpenSecretCloud/opensecret recorded 2026-06-17

  AGPL-3.0 OpenSecret platform; AWS Nitro enclave / TEE confidential-computing architecture

• https://github.com/OpenSecretCloud/opensecret/blob/master/LICENSE recorded 2026-08-12

  the OpenSecret platform repository LICENSE is the GNU Affero General Public License Version 3; the GitHub repo API reports the SPDX id AGPL-3.0

• https://github.com/OpenSecretCloud/opensecret/blob/master/README.md recorded 2026-08-12

  the backend is "the open-source Rust backend for confidential AI applications such as Maple" and builds from the Nix flake; "Billing and feature flags are optional external HTTP APIs whose administrative credentials remain in the backend; their server implementations are not part of this repository setup"

Launched Jan 2025; vendor reports "5x user growth in the last six months", >90% month-over-month paid retention, and "billions of tokens" in year one, but no absolute user count is published. Self-reported figures only, hence low confidence.

• https://blog.trymaple.ai/one-year-of-private-ai-how-maple-ai-made-encryption-easy/ recorded 2026-08-13

  launch date (Jan 2025); 5x growth, >90% retention, billions of tokens processed

Maple runs several open-weight models with image analysis, voice, document upload and live web search in end-to-end encrypted chat, and adds Team plans and a drop-in API through Maple Proxy. It remains a focused private-chat product without a documented agentic tool-use ecosystem beyond web search.

• https://blog.trymaple.ai/maple-ai-model-guide-with-example-prompts/ recorded 2026-09-29

  the page lists the models "gpt-oss-120b", "kimi-k2.5", "deepseek-r1-0528", "llama-3.3-70b", "qwen3-vl-30b" and "leon-se/gemma-3-27b-it-fp8-dynamic", says "Image processing requires more processing power. Starter+ plans help us cover these costs" for image models, links "Introducing Maple Proxy: OpenAI-Compatible API Access to Private LLMs", says the models run "in confidential computing environments with end-to-end encryption", and carries a banner "This guide is outdated. Do not use info until it has been updated for the latest models"

• https://blog.trymaple.ai/one-year-of-private-ai-how-maple-ai-made-encryption-easy/ recorded 2026-09-29

  the first-year recap says "In our first year, we shipped voice, document upload, live web search, cutting-edge reasoning models, and apps for major platforms" alongside "Team plans for organizations, and the Maple Proxy API", and "The right to verify means cryptographic attestation"