Deployment Profiles¶

Kamerplanter is modular by design. You decide which components to run — from a lean setup on a Raspberry Pi to a full multi-tenant deployment on Kubernetes. This page helps you find the right profile for your use case.

Component Overview¶

Every Kamerplanter installation consists of a core (always required) and optional components that you enable as needed.

Core (always active)¶

Optional Components¶

Profiles at a Glance¶

The following matrix shows five predefined profiles. Each profile is a recommendation — you can always add or remove individual components.

Minimal¶

Target audience¶

You want to try Kamerplanter quickly or only have a few houseplants. A Raspberry Pi ⅘ or an old laptop is sufficient. You need neither login nor AI.

Requirements¶

• Docker + Docker Compose
• 1 GB free RAM, 2 GB disk space
• Raspberry Pi 4 (2 GB), Raspberry Pi 5, NUC, laptop

Active components¶

• Backend + Frontend
• ArangoDB + Valkey
• Celery Worker + Beat
• AI assistant
• TimescaleDB
• Home Assistant
• Knowledge Service / RAG

Example configuration¶

services:
  arangodb:
    image: arangodb:3.11
    # ...

  valkey:
    image: valkey/valkey:8-alpine
    # ...

  backend:
    build: ./src/backend
    environment:
      KAMERPLANTER_MODE: light
      AI_DEFAULT_PROVIDER: none
      TIMESCALEDB_ENABLED: "false"
      VECTORDB_ENABLED: "false"
    depends_on: [arangodb, valkey]

  celery-worker:
    build: ./src/backend
    command: celery -A app.tasks worker --loglevel=info
    depends_on: [arangodb, valkey]

  celery-beat:
    build: ./src/backend
    command: celery -A app.tasks beat --loglevel=info
    depends_on: [arangodb, valkey]

  frontend:
    build: ./src/frontend
    environment:
      KAMERPLANTER_MODE: light
    depends_on: [backend]

What you gain by upgrading¶

Without the AI assistant you get no automatic care tips or diagnostics. You can add Ollama at any time without losing data.

Hobby¶

Target audience¶

You have 10--50 plants and a home server (NAS, old desktop, NUC). You want AI-powered care tips, but your data should not leave your network. You do not need login — you are the only user.

Requirements¶

• Docker + Docker Compose
• 4 GB free RAM (8 GB with 7B model), optional GPU
• Home server, NUC, desktop PC

Active components¶

• Backend + Frontend
• ArangoDB + Valkey
• Celery Worker + Beat
• Ollama (local language model)
• Knowledge Service / RAG (optionally enabled)
• TimescaleDB
• Home Assistant (optional)
• External enrichment (optional)

Example configuration¶

services:
  # ... core as in Minimal ...

  backend:
    build: ./src/backend
    environment:
      KAMERPLANTER_MODE: light
      AI_DEFAULT_PROVIDER: ollama
      AI_OLLAMA_URL: http://ollama:11434
      AI_OLLAMA_MODEL: gemma3:4b
      TIMESCALEDB_ENABLED: "false"
    depends_on: [arangodb, valkey]

  ollama:
    image: ollama/ollama:latest
    volumes:
      - ollama_models:/models
    # GPU passthrough (optional):
    # deploy:
    #   resources:
    #     reservations:
    #       devices:
    #         - capabilities: [gpu]

What you gain by upgrading¶

Without full mode you cannot invite additional users. Without TimescaleDB, sensor data is not stored long-term. Both can be enabled later.

Standard¶

Target audience¶

You are an engaged hobbyist or run a small community garden. Multiple people should have their own accounts. You want AI tips and optionally store sensor data long-term.

Requirements¶

• Docker Compose or Kubernetes cluster
• 4--6 GB free RAM
• Server, NUC, or small K8s cluster

Active components¶

• Backend + Frontend
• ArangoDB + Valkey
• Celery Worker + Beat
• Ollama (local language model)
• External enrichment (GBIF + Perenual)
• Knowledge Service / RAG (optional)
• TimescaleDB (optional)
• Home Assistant (optional)

Example configuration¶

services:
  # ... core + Ollama ...

  backend:
    build: ./src/backend
    environment:
      KAMERPLANTER_MODE: full
      AI_DEFAULT_PROVIDER: ollama
      AI_OLLAMA_URL: http://ollama:11434
      AI_OLLAMA_MODEL: gemma3:4b
      JWT_SECRET_KEY: ${JWT_SECRET_KEY}  # openssl rand -hex 32
      PERENUAL_API_KEY: ${PERENUAL_API_KEY}
      TIMESCALEDB_ENABLED: ${TIMESCALEDB_ENABLED:-false}
    depends_on: [arangodb, valkey]

controllers:
  backend:
    containers:
      main:
        env:
          KAMERPLANTER_MODE: full
          AI_DEFAULT_PROVIDER: ollama
          AI_OLLAMA_URL: http://ollama:11434
          AI_OLLAMA_MODEL: gemma3:4b
          TIMESCALEDB_ENABLED: "false"

What you gain by upgrading¶

Without TimescaleDB there is no automatic downsampling of sensor data. Without Home Assistant there is no automatic sensor collection or actuator control. Without the Knowledge Service / RAG there are no context-enriched AI responses from the knowledge base.

Professional¶

Target audience¶

You run professional indoor growing or a large community garden with role management. Sensors and actuators are connected via Home Assistant. You want seamless time-series storage, AI diagnostics with RAG context, and cloud fallback for the language model.

Requirements¶

• Kubernetes cluster (3+ nodes recommended)
• 6--8 GB RAM for Kamerplanter pods
• Home Assistant instance on the network
• Optional: GPU node for faster AI inference

Active components¶

• Backend + Frontend
• ArangoDB + Valkey
• Celery Worker + Beat
• Ollama + cloud fallback (OpenAI or Anthropic)
• Knowledge Service + VectorDB + Embedding Service
• Reranker Service (cross-encoder re-ranking)
• TimescaleDB
• Home Assistant
• External enrichment (GBIF + Perenual)

Example configuration¶

controllers:
  backend:
    containers:
      main:
        env:
          KAMERPLANTER_MODE: full
          AI_DEFAULT_PROVIDER: ollama
          AI_OLLAMA_URL: http://ollama:11434
          AI_OLLAMA_MODEL: mistral:7b
          AI_FALLBACK_PROVIDER: openai
          AI_OPENAI_API_KEY:
            secretKeyRef:
              name: kamerplanter-secrets
              key: openai-api-key
          TIMESCALEDB_ENABLED: "true"
          TIMESCALEDB_HOST: timescaledb
          HA_URL: http://homeassistant.home:8123
          HA_ACCESS_TOKEN:
            secretKeyRef:
              name: kamerplanter-secrets
              key: ha-access-token
          PERENUAL_API_KEY:
            secretKeyRef:
              name: kamerplanter-secrets
              key: perenual-api-key

  timescaledb:
    enabled: true

  knowledge-service:
    enabled: true
    containers:
      main:
        env:
          RERANKER_URL: "http://kamerplanter-ki-reranker-service:8081"
          RERANKER_INITIAL_K: "20"
          RERANKER_TOP_K: "5"

  reranker-service:
    enabled: true
    containers:
      main:
        env:
          RERANKER_MODEL: "bge-reranker-v2-m3"

  embedding-service:
    enabled: true

  vectordb:
    enabled: true

What you gain by upgrading¶

In the Professional profile you run a single instance for your organization. The SaaS profile adds multi-tenant isolation, horizontal scaling, and cloud AI as the primary provider.

SaaS / Multi-Tenant¶

Target audience¶

You operate Kamerplanter as a platform for multiple independent tenants (gardens, businesses, communities). Each tenant has its own data, roles, and settings. You need horizontal scaling and reliable cloud AI.

Requirements¶

• Kubernetes cluster with autoscaling
• 8+ GB RAM for Kamerplanter pods
• Managed database services recommended (ArangoDB Oasis, managed PostgreSQL)
• Cloud AI provider account (OpenAI or Anthropic)

Active components¶

• Backend + Frontend (multiple replicas)
• ArangoDB + Valkey
• Celery Worker (multiple replicas) + Beat
• Cloud AI (OpenAI / Anthropic)
• Knowledge Service + VectorDB + Embedding Service
• TimescaleDB
• External enrichment (GBIF + Perenual)
• Home Assistant (optional, tenant-specific)

Example configuration¶

controllers:
  backend:
    replicas: 3
    containers:
      main:
        env:
          KAMERPLANTER_MODE: full
          AI_DEFAULT_PROVIDER: openai
          AI_OPENAI_MODEL: gpt-4o-mini
          TIMESCALEDB_ENABLED: "true"

  celery-worker:
    replicas: 2

  frontend:
    replicas: 2

Build Your Own Profile¶

The profiles above are recommendations. You can enable or disable any component individually by setting the corresponding environment variables:

In Docker Compose, enable optional services via profiles:

# Core only:
docker compose up -d

# With Ollama and TimescaleDB:
docker compose --profile ollama --profile timescaledb up -d

# With RAG (Knowledge Service + VectorDB + Reranker):
docker compose --profile ollama --profile timescaledb --profile vectordb up -d

For a complete list of all environment variables, see Environment Variables.

Decision Guide¶

The following flowchart helps you find a suitable profile:

flowchart TD
    A[How many users?] -->|Just me| B{Do you need AI tips?}
    A -->|2-10 people| D{Kubernetes available?}
    A -->|10+ / tenants| G[SaaS / Multi-Tenant]

    B -->|No| C[Minimal]
    B -->|Yes| E[Hobby]

    D -->|No| F[Standard\nDocker Compose]
    D -->|Yes| H{Sensors / HA?}

    H -->|No| F2[Standard\nKubernetes]
    H -->|Yes| I[Professional]

Frequently Asked Questions¶

Can I upgrade to a larger profile later?¶

Yes. All profiles use the same database. You can add components at any time (e.g., enable Ollama, start TimescaleDB, switch from light to full mode) without losing data. When switching from light to full mode, you need to set a password for the existing system user once.

Can I run Ollama on a Raspberry Pi?¶

Yes, starting with the Raspberry Pi 5 with 8 GB RAM. Use a small model like llama3.2:3b. Response times are 15--30 seconds per tip — acceptable but not fast. The Raspberry Pi 4 does not have sufficient performance for larger models.

Do I need TimescaleDB without sensors?¶

No. Without automatic sensor data collection (IoT/MQTT or Home Assistant), TimescaleDB provides no benefit. Manual measurements (pH, EC) are stored in ArangoDB. You can enable TimescaleDB later when you connect sensors.

What happens if I do not configure an AI provider?¶

Kamerplanter works fully without AI. When AI_DEFAULT_PROVIDER=none is set (or no provider is configured), the AI tip cards are not shown in the interface. All rule-based features (phase control, fertilization plans, care reminders) operate independently of the AI provider.

See also¶

• Light Mode — Details on running without authentication
• AI Provider Setup — Configure Ollama, OpenAI, Anthropic, and other providers
• Home Assistant Integration — Sensor and actuator integration
• Environment Variables — Complete variable reference
• Kubernetes — Cluster setup and deployment
• Infrastructure — Skaffold Profiles — Skaffold modules (-m ki) for the AI stack