Skip to content

Overview

Flowtig.com is a modular, multi-tenant application platform designed to power independent SaaS services within a unified ecosystem.

Rather than building isolated tools, Flowtig provides a structured foundation where services share authentication, billing, permissions, and infrastructure — while remaining independently scalable and logically separated.

It is both a product suite and a system architecture.

Architecture at a Glance

Flowtig follows a strict separation of concerns:

  • Core Layer – Identity, authentication, tenant management, subscriptions
  • Service Layer – Independent domain applications (Time Tracking, Invoices, Construction Log, etc.)
  • Gateway Layer – Unified entry point, cross-app navigation, client switching
  • Infrastructure Layer – Containerized deployment, CI/CD pipelines, background tasks, storage

Each client operates in an isolated data scope, ensuring data integrity while enabling shared platform features.

The result is a system that behaves like a suite — but is engineered like a platform.

flowchart TB

  %% Clients
  subgraph Clients
    WEB[Web UI<br/>Next.js]
    MAC[macOS Apps<br/>SwiftUI]
    FUT[Future Clients]
  end

  %% API
  subgraph API
    GQL[GraphQL API<br/>Service Domain]
    REST[REST API<br/>Meta & Administration]
  end

  %% Core Layer
  subgraph Core["Core Layer"]
    AUTH[Authentication & Identity]
    TEN[Tenant Management]
    SUB[Subscriptions & Billing]
    PERM[Roles & Permissions]
  end

  %% Service Layer
  subgraph Services["Service Layer"]
    W[Worktime]
    I[Invoices]
    C[Construction Log]
    K[Contacts]
    O[Other Services]
  end

  %% Infrastructure
  subgraph Infra["Infrastructure Layer"]
    DOCK[Containers]
    CI[CI/CD Pipelines]
    TASK[Background Tasks<br/>Celery]
    DB[Databases]
    OBJ[Object Storage]
  end

  %% Flow Connections
  WEB --> GQL
  WEB --> REST
  MAC --> GQL
  FUT --> GQL

  GQL --> AUTH
  REST --> AUTH

  AUTH --> TEN
  TEN --> PERM
  TEN --> SUB

  PERM --> W
  PERM --> I
  PERM --> C
  PERM --> K
  PERM --> O

  W --> DB
  I --> DB
  C --> DB
  K --> DB
  O --> DB

  DB --> DOCK
  DOCK --> CI
  DOCK --> TASK
  DOCK --> OBJ

Multi-Tenant by Design

Flowtig was built with tenant isolation as a first principle.

  • Separate client databases
  • Explicit permission models
  • Role-based service access
  • Fine-grained member-level authorization

Every action is contextual to a client and a service. No hidden global state. No accidental cross-tenant leakage.

Services as First-Class Citizens

Each Flowtig service is:

  • Independently deployable
  • Permission-aware
  • Subscription-aware
  • UI-consistent with the ecosystem

Current service categories include:

  • Worktime & Time Tracking
  • Invoicing & Accounting
  • Construction Log
  • Contacts & Relationship Management
  • Commission & Project-based Compensation
  • macOS Companion Applications

Services integrate through shared conventions — not tight coupling.

Billing & Subscription Engine

Flowtig includes a fully integrated subscription model:

  • Plan subscriptions (with seat limits and durations)
  • Add-on services
  • Extra user bookings
  • Automatic invoice generation
  • Extendable billing logic

The accounting system is not an afterthought — it is part of the platform core.

Developer-Centric Foundation

Flowtig is engineered for long-term maintainability:

  • Clear GraphQL boundaries
  • Strict schema ownership
  • Modular Django apps
  • Typed frontend integrations
  • Structured CI/CD workflows
  • Container-first infrastructure

Architectural decisions are documented and reproducible.

This documentation exists not only to explain the system — but to preserve its intent.

Design Principles

Flowtig is built around a few non-negotiable ideas:

Modularity

Each service must be independently understandable and maintainable.

Explicitness

No magic behavior. No hidden state. Clear boundaries.

Longevity

Small teams. Sustainable code. No short-lived hacks.

Transparency

Full control over hosting, deployment, and data ownership.

Who This Documentation Is For

This documentation is intended for:

  • Developers working on the platform
  • Contributors extending services
  • Integrators building custom workflows
  • Curious readers exploring system design

It is both technical reference and architectural journal.

The Bigger Picture

Flowtig is not optimized for trend cycles. It is optimized for clarity, ownership, and evolution.

The goal is not to grow complexity. The goal is to grow capability without losing structure.

This documentation provides the architectural and technical foundation of the Flowtig platform.