MaxKB Community Edition

Open-source knowledge-base, RAG and agent-workflow platform deployable into an Alibaba Cloud account.

10 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

MaxKB v2.10.9-lts security update

MaxKB v2.10.9-lts fixes cross-workspace authorization, stored XSS, secret exposure, SSRF, provider-key disclosure and unauthorized data access.

Scope: MaxKB Community LTS; the release does not publish one universal affected-version range.

Workspace membership, custom tools, provider configuration, anonymous access and reachable metadata or internal services determine applicability.

Action: Upgrade to v2.10.9-lts or later and retest workspace, tool, provider and anonymous-access boundaries.

Primary source · GHSA-5545-9jgw-jg2g · GHSA-mgph-cpg8-q442 · Reviewed 2026-11-19

What lands where

  1. Supplied by

    Vendor or project

    Create the documented MaxKB Community Edition service instance through Alibaba Cloud Compute Nest, or use the publisher-documented Alibaba Cloud Marketplace image on a customer ECS server.

  2. Operated by

    Your team

    Customer manages the ECS host, VPC and security-group exposure, administrator credentials, persistent PostgreSQL data, backups, upgrades, capacity and credentials for model and tool integrations.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodCreate the documented MaxKB Community Edition service instance through Alibaba Cloud Compute Nest, or use the publisher-documented Alibaba Cloud Marketplace image on a customer ECS server.
InfrastructureServers / containers
Alibaba Compute Nest provisions the Community Edition on customer-selected ECS capacity, VPC, VSwitch, zone and region. The application and its persistent PostgreSQL/pgvector data run as provisioned server workloads rather than a serverless or vendor-managed service.
Licensing modelOpen Source / Open Core
This listing is scoped to the GPLv3 Community Edition. Professional and Enterprise editions add commercially licensed X-Pack capabilities, deployment options and vendor support; their entitlements are not implied by this classification.
LicenseGNU General Public License version 3 for Community Edition. Professional and Enterprise editions add separately licensed features and support.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

8 of 12 fields researched (67%) · 8 documented · 0 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
DocumentedEvidence and scope for Marketplace delivery

Alibaba Cloud documents a Community Edition Compute Nest service that creates an ECS-based deployment in the customer’s selected network. The vendor’s separately priced Marketplace Professional Edition is a different entitlement; its pricing does not price this Community listing.

Provider-documented Community Compute Nest service; separate from the Professional Marketplace offer · Source ↗ · Edition pricing and Professional Marketplace distinction ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Single sign-on
Not availableEvidence and scope for Single sign-on

The edition matrix excludes LDAP, OIDC, CAS, OAuth2 and SAML2 single sign-on from Community Edition and includes them in Professional/Enterprise. This does not establish SCIM provisioning.

Community Edition only; commercial edition entitlements differ · Source ↗ · Reviewed 2026-11-16

Explicitly unsupported · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

The edition matrix reserves full RBAC and system-operation logs for Professional/Enterprise. The online installer publishes default administrator credentials; replace them and configure access controls before exposing an instance. Current review: v2.10.9-lts fixes cross-workspace file and SKILL access/deletion, stored XSS with account-takeover impact, custom-tool secret exposure, multiple SSRF paths, anonymous provider API-key disclosure and unauthorized conversation or knowledge-base access. Upgrade and retest workspace and provider boundaries.

MaxKB Community LTS; the release does not publish one universal affected-version range · Source ↗ · Prior security-controls source ↗ · Online installation and default account ↗ · GHSA-5545-9jgw-jg2g ↗ · GHSA-mgph-cpg8-q442 ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Air-gapped operation
DocumentedEvidence and scope for Air-gapped operation

The v2 guide documents transferring a Community offline-installer archive, configuring it locally and applying offline upgrades after backups. That confirms offline application installation; models, embeddings, integrations and their dependencies must also be available inside the isolated environment.

MaxKB v2 Community offline installation and upgrades; not a claim that external model APIs work disconnected · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The current v2 guide uses registry.fit2cloud.com/maxkb/maxkb and persists data at /opt/maxkb. The English legacy guide uses different images/data paths; do not mix those configurations or assume compatibility with an older cloud package. Select and test a matching release.

Current upstream v2 container example; untagged image is not an immutable release · Source ↗ · Versioned offline-installer example ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The current v2 guide specifies at least 4 CPU cores, 8 GB RAM and 100 GB disk, with Docker 26+ recommended or the bundled Docker. Community package architecture and single-node/cold-standby limits follow the edition matrix; model hosting needs separate sizing.

Community v2 application baseline, excluding model/GPU services and workload-specific capacity · Source ↗ · Edition architecture/deployment matrix ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

This listing is scoped to the GPLv3 Community Edition. Professional and Enterprise editions add commercially licensed X-Pack capabilities, deployment options and vendor support; their entitlements are not implied by this classification.

MaxKB Community Edition: software license terms; infrastructure and operating costs are separate · Source ↗ · Edition and license conditions ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

MaxKB v2.10.9-lts was published November 19, 2026. It fixes cross-workspace authorization, stored XSS, secret exposure, SSRF, provider-key disclosure and unauthorized conversation or knowledge-base access issues.

Upstream MaxKB Community LTS release; commercial editions and deployment packages may differ · Source ↗ · Prior reviewed release context ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (4 not researched)
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

The Compute Nest deployment requires RAM permissions with full access to ECS, VPC and ROS plus Compute Nest user access; review and reduce deployment privileges after provisioning where practical. Community Edition is single-tenant, x86-64 only and supports single-node or cold-standby deployment rather than Enterprise clustering. RBAC, SSO, audit logs, open API access, conversation-user authorization and several enterprise integrations are reserved for paid editions. Current upstream v2 installation guidance calls for at least 4 CPU cores, 8 GB RAM and 100 GB of disk, exposes the web service on port 8080 and supplies default administrator credentials that must be changed immediately. The publisher recommends offline installation for production and requires a database backup before upgrades. Public or separately hosted model, embedding, reranking and tool providers can receive application data even when MaxKB itself runs in the customer account. The current upstream v2 container image and persistence paths differ from the legacy English guide; check the release packaged by the cloud installer before applying upstream configuration or upgrades. MaxKB v2.10.9-lts fixes multiple cross-workspace access and deletion flaws, stored XSS with account-takeover impact, custom-tool secret exposure, SSRF paths including possible cloud-credential theft, anonymous provider API-key disclosure and unauthorized conversation or knowledge-base access. Upgrade the LTS line and retest workspace, tool and provider boundaries.

Community & maintenance

The official repository publishes an active versioned release stream and public contribution, code-of-conduct and security workflows. This establishes public project maintenance but does not certify any adopter's hosting topology.

Category fit

AI applications & RAG
Self-hosted knowledge ingestion, document vectorization, RAG, question-answering and agent-workflow platform with configurable model providers.
AI tools & infrastructure
Customer-hosted agent and workflow platform with knowledge bases, MCP and tool integrations, and configurable language, embedding, reranking and multimodal models.

Compare within AI applications & RAG

  • AnythingLLM DockerSelf-hosted application for document-grounded AI chat, retrieval and agents.
    • AWS
    • Google Cloud
    • Railway
    Customer-operated · Open Source / Open Core
  • Dify Self-HostedVisual AI application and RAG workflow platform available as a self-hosted container stack.
    • Alibaba Cloud
    Customer-operated · Source Available
  • Langflow Self-HostedVisual AI workflow and agent builder with Docker and persistent PostgreSQL deployment.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • LibreChat Self-HostedSelf-hosted multi-model AI chat, agent and retrieval platform with documented Railway and DigitalOcean deployments.
    • DigitalOcean
    • Railway
    Customer-operated · Open Source / Open Core
  • Onyx Self-HostedSelf-hosted enterprise search and AI assistant platform with connectors and retrieval infrastructure.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Open WebUI Self-HostedSelf-hosted AI chat and knowledge interface for local model servers and cloud APIs.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Source Available
  • RAGFlowDocument processing and retrieval platform for building RAG and agentic knowledge applications.
    • AWS
    • Azure
    • Google Cloud
    • Alibaba Cloud
    • Railway
    Customer-operated · Open Source / Open Core

These products address related workflows; read their category-fit notes before comparing scope. See all of AI applications & RAG →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • MaxKB Community Edition service instance in Alibaba Compute Nest ↗ · Alibaba Cloud

      Provider guide · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.

      Alibaba Cloud documents creation of a MaxKB Community Edition service instance in a customer-selected region, zone, VPC and VSwitch using customer-selected ECS capacity and billing. The deployed application is reached through the ECS public address on port 8080. The workflow requires broad ECS, VPC, ROS and Compute Nest permissions and returns default administrator credentials that must be changed.

    • MaxKB image deployment from Alibaba Cloud Marketplace ↗ · Alibaba Cloud

      Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.

      The publisher documents selecting the MaxKB image while purchasing an Alibaba Cloud server, starting the image and opening port 8080 in the customer's security group. It recommends at least 4 CPU cores and 8 GB RAM and instructs administrators to replace the default password after first login.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory