Hyperforge is a Python monorepo for building and running agentic workflows on top of NucliaDB. It contains the Hyperforge orchestration/runtime service, a NucliaDB Agentic API service, and a set of reusable Hyperforge agent packages.
hyperforge/: core framework, REST API, workflow runtime, persistence, broker integration, and the optional web UI source.nucliadb_agentic_api/: NucliaDB-facing agentic API with ASK/search endpoints and MCP integrations.agents/: first-party Hyperforge agent packages that add workflow capabilities such as NucliaDB access, HTTP calls, MCP tools, static context, rephrasing, summarization, and routing.hyperforge/frontend/: Vue UI source bundled by the Hyperforge package when built..github/workflows/: package build and release workflows for the core package and agent packages.
The workspace is managed with uv and Python 3.10 or newer.
Core packages:
hyperforge: agentic framework runtime and API.nucliadb_agentic_api: NucliaDB Agentic API service.
Agent packages:
hyperforge_conditionalhyperforge_externalhyperforge_generatehyperforge_historicalhyperforge_httphyperforge_mcphyperforge_nucliadbhyperforge_passthroughhyperforge_relatedhyperforge_remihyperforge_rephrasehyperforge_restarthyperforge_restrictedhyperforge_smarthyperforge_statichyperforge_static_stringhyperforge_summarize
Install dependencies:
uv syncInstall development dependencies:
uv sync --group devRun formatting:
make fmtRun linting and type checks:
make lintRun tests:
uv run pytestStart the Hyperforge API:
uv run hyperforge-apiStart the NucliaDB Agentic API:
uv run nucliadb-agentic-apiBoth services read configuration from environment variables through Pydantic settings. Important settings include NucliaDB reader/writer/search URLs, optional NucliaDB API keys, Valkey/Redis URL, service ports, and module loading configuration.
This repository is licensed under the Apache License 2.0. See LICENSE.
Before publishing a release, review:
- Package metadata in each
pyproject.toml, especially project URLs and package descriptions. - Dockerfiles, which may need deployment-specific updates for public builds.
- Generated test cassettes and fixtures to ensure they do not contain secrets.
- CI/CD workflow secrets and publishing credentials.
Contributions are welcome. Please format the code with make fmt, run
make lint, and run the relevant tests before opening a pull request.
Disclaimer: This is not an officially supported Progress Software Corporation product.