Fagoon Upgrade
Self-hosted AI platform with workflow automation, agents, chat, and API generation.
Build AI workflows visually, publish them as REST APIs, deploy agents, and chat with LLMs — all running on your own machine.
Quick Start
Prerequisites
- Docker Desktop — Download here
- Python 3.11+ — Download here
- pipx (recommended) — Install with:
pip install pipx
Install & Run
# Install the CLI
pipx install fagoon-upgrade
# Start the platform
fagoon up
On first run, you'll see a setup wizard:
Welcome to Fagoon!
Let's set up your AI platform.
How would you like to power your AI?
1) I have an API key (OpenAI, Gemini, Groq, etc.)
2) Use local Ollama model (free, runs on your machine)
3) Skip for now (configure later in the UI)
Choose [1/2/3]:
Access the Platform
| Service | URL |
|---|---|
| Frontend | http://localhost:3000 |
| Backend | http://localhost:8000 |
Features
- Visual Workflow Builder - Drag-and-drop canvas with 20+ node types
- Workflow-as-API - Publish any workflow as a REST endpoint with API key auth
- AI Agents - Conversational agents with memory and tool use
- Chat Interface - Chat with any LLM provider through a unified UI
- Multi-Provider - OpenAI, Gemini, Groq, Anthropic, Ollama
- Self-Hosted - Your data stays on your machine
CLI Commands
fagoon up # Start the platform (lite mode)
fagoon up --full # Start with Redis + Celery (multi-worker)
fagoon up --ollama # Start with local Ollama LLM
fagoon down # Stop the platform
fagoon logs -f # Follow live logs
fagoon status # Check if running
fagoon update # Pull latest version and restart
fagoon config set KEY=VALUE # Set configuration
fagoon config show # Show current config
fagoon db set-url URL # Switch database
Workflow-as-API
Publish any workflow as a callable REST API:
curl -X POST http://localhost:8000/api/v1/workflow-api/your-slug/execute \
-H "X-API-Key: wfapi_your_key_here" \
-H "Content-Type: application/json" \
-d '{"input": "Hello from my app"}'
Response:
{
"success": true,
"execution_id": "uuid",
"status": "COMPLETED",
"output": {
"output_text": "AI generated response",
"model": "gemini-2.5-flash"
},
"usage": { "duration_ms": 2500 }
}
Deployment Modes
Lite Mode (Default)
Single-user, no Redis/Celery. Perfect for personal use.
fagoon up
Full Mode
Multi-worker with Redis + Celery. For production.
fagoon up --full
With Ollama (Local LLM)
Free, offline AI using local models.
fagoon up --ollama
Docker Compose (Direct)
services:
app:
image: ghcr.io/fagoon-ai/upgrade:2.0.4
ports:
- "8000:8000"
- "3000:3000"
environment:
LITE_MODE: "true"
DATABASE_URL: postgresql+asyncpg://fagoon:fagoon@db:5432/fagoon
depends_on:
db: { condition: service_healthy }
db:
image: pgvector/pgvector:pg16
environment:
POSTGRES_USER: fagoon
POSTGRES_PASSWORD: fagoon
POSTGRES_DB: fagoon
volumes:
- fagoon_db:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U fagoon"]
interval: 5s
timeout: 5s
retries: 10
volumes:
fagoon_db:
Environment Variables
| Variable | Default | Description |
|---|---|---|
| LITE_MODE | true | true = single-process, false = Redis+Celery |
| DATABASE_URL | auto | PostgreSQL connection string |
| JWT_SECRET | auto | Secret for JWT tokens |
| GEMINI_API_KEY | — | Google Gemini API key |
| OPENAI_API_KEY | — | OpenAI API key |
| GROQ_API_KEY | — | Groq API key |
| OLLAMA_BASE_URL | — | Ollama server URL |
| WEB_CONCURRENCY | 1 | Number of workers |
Troubleshooting
"Cannot connect to Docker daemon" — Start Docker Desktop and wait for it to load.
"Port 3000/8000 already in use" — Stop other services on those ports.
Platform won't start:
fagoon logs -f # Check logs
fagoon down # Stop
fagoon up # Restart
Reset everything:
fagoon down
docker volume rm fagoon_db fagoon_data
fagoon up
Tech Stack
- Backend: Python, FastAPI, SQLAlchemy, PostgreSQL, pgvector
- Frontend: Next.js, React, TailwindCSS, React Flow
- Workflow Engine: Custom DAG executor with 20+ node types
- Task Queue: Celery + Redis (full mode)
- Container: Docker, Docker Compose
Links
- Website: fagoonai.com
- PyPI: pypi.org/project/fagoon-upgrade
- Docker:
docker pull ghcr.io/fagoon-ai/upgrade:2.0.4 - GitHub: github.com/Fagoon-AI/upgrade
License
MIT
Metadata
Release files for fagoon-upgrade 2.1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| fagoon_upgrade-2.1.7.tar.gz | 7.7 MB | With provenance | Details for fagoon_upgrade-2.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fagoon_upgrade-2.1.7-py3-none-any.whl | Python 3 | none | any | Details for fagoon_upgrade-2.1.7-py3-none-any.whl |
Total release size: 8.4 MB
Release files / fagoon_upgrade-2.1.7.tar.gz
| Download URL | fagoon_upgrade-2.1.7.tar.gz |
|---|---|
| Size | 7.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
66d041168d25b344603a9fc3da24c20524bd60d6e82f580104e09e5fbe756406
|
|
BLAKE2b-256 checksum How to use checksums |
35bf75ddf6bb83f26cb3295a029f23001bc5a8eaf807194314bad149d50ba839
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 22, 2026.
Transparency logRelease files / fagoon_upgrade-2.1.7-py3-none-any.whl
| Download URL | fagoon_upgrade-2.1.7-py3-none-any.whl |
|---|---|
| Size | 675.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fc7b90d85886b935d5b468bfce768f6bb05b48d06d96de94431d2aaf6e2dda50
|
|
BLAKE2b-256 checksum How to use checksums |
4e4d386fe180e54edb8bd37ce8e3d5bb1d44cacdfa8b7e2940d8e22ad81fb4f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 22, 2026.
Transparency logSecurity for fagoon-upgrade 2.1.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for fagoon_upgrade-2.1.7.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.