Project orchestrator - for AI, Agentic

🏅 Setting up SaaS for application with orchestrator and Agentic AI projects

Here I will describe and document my journey with setting up software to be used for experiments in relation to project orchestrator. Steps include overview and details that is relevant from building core and secure foundation to setting up needed software stack and develop and deploy multiple applications.

---

🏭 Overview	📆 Status	🌐 Link	📝 Notes
SaaS Orchestrator	Setup January/2026	Orchestrator	orchestrator.dk
Agentic AI prototypes	Setup January/2026	Agentic
Agentic AI prototypes	Setup January/2026	ServerSide
Pydantic contract	Setup February/2026	ServerSide	Note pydantic, deterministic
Install next	To come January/2026	WIP	with notes

---

Initial Architecture overview.

This diagram shows how the system can evolve from a single-agent prototype into a multi-tenant orchestrator without major architectural changes.

At the top level, users or automation systems (web UI, CLI, cron jobs) interact with a central orchestrator. The orchestrator routes requests to the appropriate tenant context.

Each tenant owns one or more agents. For example, Tenant A may run both Agent A1 and Agent A2, while Tenant B runs a different agent with its own configuration and purpose.

All agents share the same underlying infrastructure: a common API layer, filesystem access, and centralized run history. Isolation is achieved at the configuration and routing level rather than by duplicating infrastructure.

This design supports “mini sovereign agents” — independently controlled agents operating within a shared platform — while remaining lightweight and understandable.

flowchart TB
    UI[Web UI / CLI / Cron]

    subgraph Orchestrator
        T1[Tenant A]
        T2[Tenant B]
    end

    subgraph TenantA["Tenant A"]
        A1[Agent A1]
        A2[Agent A2]
    end

    subgraph TenantB["Tenant B"]
        A3[Agent A3]
    end

    subgraph Infra["Shared Infrastructure"]
        API[Agent API]
        FS[File System]
        LOG[Run History]
    end

    UI --> Orchestrator
    Orchestrator --> T1
    Orchestrator --> T2

    T1 --> A1
    T1 --> A2
    T2 --> A3

    A1 --> API
    A2 --> API
    A3 --> API

    API --> FS
    API --> LOG

---

Last updated: January 2026
Source: Cantaloop Aps.