Browse documentation

๐Ÿงญ Start Here

Blackcap Overview โœจ Blackcap Feature Catalog ๐Ÿค– AI Features ๐Ÿงฑ Technology, Administration, and Reliability Installation First Run

๐Ÿ“˜ User Guides

Administration and Operations Platform Configuration Organization Configuration Email and Consent Management

๐Ÿš€ Deploy Blackcap

Platform Stacks and Raspberry Pi Hardware Raspberry Pi Deployment Raspberry Pi Client Services GCP Deployment Packaged Blackcap deployment Application Updates After Your First Blackcap Login: Self-Hosted Setup Guide Blackcap Release Notes Environment Variables and Secrets Reverse Proxy and TLS Background Jobs and Schedules

๐Ÿ› ๏ธ Administer Blackcap

Organizations Users, Permissions, and Authentication Configuration Workspace Backups and Restore Database Administration Regression Testing Performance and Job Status Audit, Access Activity, and Logging GeoIP and Access Location Data Retention and Purge Support Chat Administration Support Requests API Tester and Postman Instance Reporting Third-Party Packages and Attribution AI Provider Usage and Billing Portals Microwave Pie licensing for Blackcap Microwave Pie licensing for Blackcap

๐Ÿฝ๏ธ Use Recipes

Recipes and the Recipe Library Recipe Import and Discovery Recipe Editing and Cache Artifacts Recipe Sharing Social Recipe Import AI Recipe Image Generation ๐Ÿช„ Adapt Recipe and ๐ŸŽฒ Variations

๐Ÿ“… Plan Meals

Meal Planner

๐Ÿ›’ Use Shopping Lists

Shopping Lists and Shop a List External and Household Shopping ๐Ÿ”— Chrome Extension Shop With

๐Ÿงบ Manage Kitchen Inventory

๐Ÿงบ Kitchen Inventory

๐Ÿ–ฅ๏ธ Use Displays

Displays and Connections Assigning and Scheduling Display Content Remote Pi Client E-Ink Rendering Menu Refresh and Rendering Noun Project Footer Images

๐Ÿง‘โ€๐Ÿณ Cook with Letโ€™s Cook

๐Ÿง‘โ€๐Ÿณ Letโ€™s Cook ๐Ÿง‘โ€๐Ÿณ Letโ€™s Cook Controls and Timers

๐Ÿค– Use and Administer AI

๐Ÿค– AI in Blackcap ๐Ÿค– AI Providers and Connections ๐Ÿค– AI Seeds and Usage Support Chat

๐Ÿ”— Use the Chrome Extension

๐Ÿ”— Blackcap Chrome Extension ๐Ÿ”— Chrome Extension Recipe Capture ๐Ÿ”— Chrome Extension Shop With ๐Ÿ”— Chrome Extension Release and Privacy

๐ŸŽฎ Play Games

Games and trivia Bramble Harvest โ€” Player Guide Flavor Lab โ€” Player Guide

๐Ÿ”Œ Integrations

Email Integration Cloud Storage Integrations Voice Assistants Shop With Integrations Authentication Providers

โš™๏ธ Develop Blackcap

Application Architecture Database Service and Data Access SQLite and PostgreSQL Database Migrations Background Job Architecture Testing Games platform โ€” current developer reference Bramble Harvest developer tools API Architecture Security and Organization Scoping UI, Icons, and Documentation Assets Blackcap-Safe Emoji Support Chat Architecture Extending Support Chat Support Chat Model Benchmark Documentation Standards Terminology

โš ๏ธ Troubleshoot Blackcap

โš ๏ธ Troubleshooting Licensing Troubleshooting Deployment Troubleshooting Display Troubleshooting Recipe Import Troubleshooting ๐Ÿค– AI Troubleshooting Backup Troubleshooting Database Troubleshooting Diagnostic Organization Clones Support Chat

Third-Party Packages and Attribution

Blackcap uses open-source and commercial third-party software. This is the in-application attribution and dependency reference page. It identifies Python distribution families declared by this repository and explains where to inspect the exact versions on a particular deployment.

Important: An inventory of package names, versions, or links is not a substitute for any license texts, copyright statements, attribution requirements, or NOTICE files that redistribution licenses require. The exact notices must be assembled and verified for the actual release artifacts (including transitive and bundled native dependencies), not inferred from this page.

Where to inspect the installed packages

  • Compiled Blackcap: On System โ†’ View Packaged Python Dependencies, inspect the immutable list of direct and resolved/transitive distributions bundled at build time. It reflects that release, not the version currently on PyPI. The dialog links back to this documentation.
  • Direct-source Blackcap (GCP/Pi): The System page's Python Package Review reflects installed libraries; the declared requirements are in requirements-cloud.txt for GCP and requirements.txt for Pi. The actual environment may contain additional transitive packages.
  • Packaged Source: Check its deployment requirements and any published build manifest. A requirements list alone does not describe the entire resolved environment.

Python packages Blackcap declares

The following names describe declared Python dependencies, not a release-specific inventory. Exact installed versions are shown in System package diagnostics and may differ from development requirements. The project links are entry points for upstream license and source information; inspect each actual distribution's LICENSE, COPYING, NOTICE, and package metadata when preparing a redistributed release. Some metadata points to additional files or multiple licenses.

Shared GCP and Raspberry Pi requirements

These distributions are declared for both GCP and Raspberry Pi installations; refer to the requirements files for the authoritative current list:

Python distribution Upstream package / license metadata
beautifulsoup4 PyPI project
blinker PyPI project
certifi PyPI project
cffi PyPI project
charset-normalizer PyPI project
click PyPI project
cryptography PyPI project
dropbox PyPI project
flask PyPI project
google-api-core PyPI project
google-api-python-client PyPI project
google-auth PyPI project
google-auth-oauthlib PyPI project
googleapis-common-protos PyPI project
greenlet PyPI project
gunicorn PyPI project
httplib2 PyPI project
idna PyPI project
itsdangerous PyPI project
jinja2 PyPI project
lemminflect PyPI project
markupsafe PyPI project
mistune PyPI project
maxminddb PyPI project
numpy PyPI project
oauthlib PyPI project
opencv-python-headless PyPI project
packaging PyPI project
pillow PyPI project
playwright PyPI project
ply PyPI project
proto-plus PyPI project
protobuf PyPI project
psycopg PyPI project
psycopg-pool PyPI project
pyasn1 PyPI project
pyasn1-modules PyPI project
pycparser PyPI project
pyee PyPI project
pymupdf PyPI project
pyparsing PyPI project
pytesseract PyPI project
pyzbar PyPI project
qrcode PyPI project
requests PyPI project
requests-oauthlib PyPI project
setuptools PyPI project
six PyPI project
soupsieve PyPI project
stone PyPI project
typing-extensions PyPI project
uritemplate PyPI project
urllib3 PyPI project
werkzeug PyPI project
openai PyPI project
anthropic PyPI project
google-genai PyPI project

Raspberry Pi hardware-only requirements

Additional Raspberry Pi hardware requirements may be present in requirements.txt but not requirements-cloud.txt:

Python distribution Upstream package / license metadata
colorzero PyPI project
gpiozero PyPI project
lgpio PyPI project
rpi-lgpio PyPI project
spidev PyPI project

Other software and externally supplied assets

The Python list does not cover all third-party components that a deployment may install, download, or redistribute:

| Component / service | How Blackcap uses it | Attribution guidance | | --- | --- | | Chromium / Playwright browser assets | Browser automation and source rendering | Check the exact browser binaries and third-party notices included with the browser distribution; the Python playwright package alone is insufficient | | Raspberry Pi display libraries and operating-system packages | SPI/GPIO, device access, local display | Check installed OS packages and any embedded hardware SDK or binary artifacts for their own licenses | | Image/OCR and native dependencies (e.g., Tesseract, ZBar) | OCR, barcode reading, image processing | Review native packages and their libraries separately from Python wrappers | | Gunicorn, Nginx, PostgreSQL, SQLite and Cloud SQL proxy | Web serving, reverse proxy and persistence, depending on deployment | Verify which components are actually redistributed versus independently installed on the host | | TheMealDB, Noun Project, FoodKeeper, source websites | Ingredient images, artwork, shelf-life data, recipe attribution | External content and service terms are separate from Python-package licenses; preserve image/source attribution where required |

This list describes possible components and integrations, not a claim that all of them are bundled with every installation.

Release-specific license and NOTICE obligations

For each distributed Blackcap Source or Compiled release, the publisher must audit what the artifact actually contains:

  1. Inventory the fully resolved packages and any bundled interpreter, browser, native binaries, JavaScript libraries, fonts, and artwork. Capture exact versions and sources, including transitive dependencies.
  2. Collect the exact applicable license texts, copyright notices and required third-party NOTICE content from those artifacts and their respective upstream sources. Escalate unknown or ambiguous licensing rather than guessing.
  3. Distribute required notices in an accessible THIRD_PARTY_NOTICES file or directory alongside the release, with any attributions required in-product. Provide an installed-app link where appropriate.
  4. Keep the notice bundle synchronized with each release and verify that the installed artifact can reach the notices without relying on Internet access.

Current limitation: This page and the System package inventory do not themselves establish that a legally complete release-specific notice bundle exists. Until license text collection and build-time enforcement are implemented, do not describe a packaged release as fully attribution-compliant solely on the basis of this list.

On this page