Andoza
Product & docs

Andoza is a self-hostable document stack

This site (andoza.app) explains the project, who it is for, and what you can build. Try a hosted environment on andoza.o27.uz, or follow the self-hosting guide below to run everything on your own servers.

Open live demoAbout the productSelf-host guide

Product

What Andoza is

Andoza brings together a web app, HTTP API, and background services so you can manage document-centric workflows in one place. Templates, uploads, and programmatic access share the same Postgres data and S3-ready object storage (MinIO in the default stack), which makes it easier to keep content consistent whether humans or integrations touch it.

Who it is for

Teams and builders who need a practical, self-hosted layer for documents and assets—not only a static website, but a small platform they can extend, audit, and run behind their own network policies.

Organizations & ops
Run on private infrastructure, keep credentials inside your perimeter, and align with compliance expectations when SaaS is not an option.
Developers & integrators
Use the API alongside the UI, wire in your own tools, or customize deployments with standard Docker workflows you already know.

What you can do

Capabilities depend on how you configure the stack, but the default architecture is built around these ideas:

  • Operate a full web application served through nginx with an API for server-side features and automation.
  • Store and serve assets via S3-compatible storage so templates and uploads have a durable home.
  • Isolate heavy work in a dedicated generator service so the API stays responsive while long-running tasks finish.
  • Authenticate users with a modern session model suitable for internal tools or customer-facing portals when configured carefully.
Public demo
Try it on andoza.o27.uz
The environment at andoza.o27.uz is meant for evaluation—not production data. Use it to explore the UI and behavior before you commit to self-hosting.
Launch demo

Why self-host

Clarity for operators

If you choose to run Andoza yourself, you get repeatable installs, visible manifests, and room to harden the stack the way your organization expects.

One installer
Pull the source, sync the official compose file from andoza.app, generate secrets, and start containers—documented step by step in the guide below.
Data stays yours
Postgres and object storage run where you deploy them, which is essential when customer or internal documents cannot leave a specific region or VPC.
Space to customize
Open-source code, environment-driven configuration, and optional container images from your registry when you outgrow local builds.
Self-host (from andoza.app)

$ curl -fsSL https://andoza.app/install.sh | bash

Self-hosting guide

Self-host with Docker

Run the full Andoza stack on your infrastructure. Official install.sh and docker-compose.yml are hosted on https://andoza.app so updates stay in one place. A separate live demo runs on andoza.o27.uz for trying the product in a browser.

Docker Compose

Quick start

curl -fsSL https://andoza.app/install.sh | bash

Regenerate .env (backup is created automatically):

curl -fsSL https://andoza.app/install.sh | bash -s -- --force
Static files
Direct URLs for scripts and compose
/install.sh/docker-compose.yml
Requirements
Linux, macOS, or Windows with Docker Desktop
  • Docker Engine (current stable recommended)
  • Docker Compose v2 (docker compose)
  • Git
  • curl

Architecture

One compose file connects every service.

PostgreSQL
Primary relational data
MinIO
S3-compatible object storage
API · Web · Generator
Node services behind nginx
Default host ports
Override via .env
Web UI7051Browser entry point (nginx)
API7050HTTP API
MinIO S3 API9000S3-compatible endpoint
MinIO Console9001Object storage admin UI