Nodante · System Architecture

Architecture

Nodante is the root node of a small network of ventures. This page traces every branch from the holding down to the infrastructure layer — and the services actually running on it today.

4Ventures

10TLS-routed domains

70+Pooled AI credentials

5minHealth-check cadence

Ventures

Four ventures run under the Nodante holding today — three of them products and operations built on top of the fourth, the infrastructure layer every branch stands on.

Live — Consumer

Dede Korkut

A story app bringing classic Anatolian tales to children — crafted typography, original illustration and narration in a calm, ad-light reading experience.

↳ dedekorkut.artbr.net

Live — Media

Channel Network

Self-healing publishing operations across messaging platforms: educational quiz channels, curated feeds and autonomous moderation.

↳ see it on the map

Live — Systems

Automation Stack

Workflow automation with a unified model-access layer — content pipelines, deduplication caches and scheduled intelligence, running unattended.

↳ automation engine detail

Foundation

Infrastructure

Self-hosted platform operations: containerised deployment, monitoring and hardened access — the ground every venture stands on.

↳ infrastructure detail

System Map

From the root down: four ventures branch directly from Nodante. Infrastructure — the foundation the other three run on — branches further into the technical layers detailed below. Every node links to its section.

Venture — Infrastructure

The layer every venture stands on

An end-to-end automation platform that produces, renders and distributes educational content across Telegram channels — around the clock, with no human in the loop — sits alongside a consumer app and a self-hosted AI gateway, all on the same hardened, self-monitoring base. An n8n orchestration layer drives every workflow, a self-hosted LiteLLM AI gateway brokers all model traffic across a large credential pool, and independent watchdog layers monitor the whole system and surface failures before anyone needs to look.

Infrastructure — Traffic & Routing

Traffic & Routing

All external traffic enters through a single reverse-proxy layer. TLS certificates are provisioned and renewed automatically, and requests reach the right service through label-based discovery — new services join the mesh without a line of manual proxy configuration. The diagram below shows the end-to-end data flow.

Infrastructure — Automation Engine

n8n

The orchestration layer at the heart of the platform, and the engine behind the Automation Stack venture. Three workflow families operate independently of one another: core engines, content production lines, and guard & maintenance jobs.

Core Engines

00. Scheduler

Computes the daily publishing plan from cron triggers and distributes it across every production line.

01. Analytics

Collects audience and membership metrics and persists them to a central reporting sheet.

02. Credential Rotation

Cycles the AI credential pool continuously, sustaining high request throughput without interruption.

TG-13. Engagement Responder

Generates organic, AI-written responses to incoming webhook interactions.

Content Channels

TG-01. English Learning

Generates English-learning content from structured source data, renders it to video and publishes to its channel.

TG-06. Verbal Reasoning

Produces verbal-logic questions with Gemini and publishes them as interactive polls.

TG-10. Past Exam Questions

Matches archived exam-question imagery against structured records and schedules publication.

TG-12. Official Announcements

Continuously monitors the national exam authority's website and relays new announcements within minutes.

Guard & Maintenance

ZZ-01. Error Workflow

Captures any failed execution across all workflows and notifies the operator instantly, with full execution context.

ZZ-02. Clean-Up

Nightly maintenance: purges temporary files, expired renders and excess logs.

Data Sync Layer

Content Cache & Replay

Mirrors structured content and media from third-party spreadsheets and file storage into a local cache, and replays outgoing writes in the background with automatic retry — production lines never wait on a third party to publish.

Infrastructure — AI Gateway

LiteLLM Proxy

Every AI call on the platform passes through a single self-hosted gateway. It presents one stable, OpenAI-compatible endpoint while load-balancing traffic across a large credential pool — sustaining high throughput and making consumption observable from a single pane.

Gateway LiteLLM Proxy

The single entry point for all model traffic. Distributes requests across a pool of 70+ upstream API credentials with automatic rotation and failover, and feeds a live operations dashboard that tracks consumption in real time.

Metrics Prometheus + Pushgateway

Collects request volume, rotation behaviour and per-container resource usage. A pushgateway lets short-lived jobs report their metrics too — nothing on the platform escapes measurement.

Infrastructure — Content Pipeline

Content Production Pipeline

Every content channel flows through the same five-stage pipeline — fully automated from source data to published media.

Source Data

Topics, questions and content plans are read from structured source sheets.

AI Generation

Gemini models draft the content through the LiteLLM gateway.

Template Composition

Generated copy is composed into a branded HTML template.

Render

A headless, FFmpeg-based pipeline turns the template into broadcast-ready video.

Distribution

The video is published to its Telegram channel and made available for direct download.

Infrastructure — Reliability

Reliability & Monitoring

The platform monitors itself. Two independent layers — a standalone Telegram service and a scheduled watchdog — catch and report failures before any human needs to look.

standalone Herald

A Telegram event listener and poll bot that runs fully independent of the orchestration stack, supervised at the host level for automatic restart on failure.

watchdog · 5 min Sentinel

Verifies the liveness of core services every five minutes; on failure it raises an instant alert to the operator and records the event as a metric for trend analysis.

Design principle: the watcher is separated from the watched. Herald and Sentinel live entirely outside the container runtime — if Docker or the orchestration layer goes down, monitoring and alerting stay up.

Infrastructure — Base Layer

Hosting & Version Control

The entire platform runs on dedicated cloud infrastructure under a strict layout and version-control discipline — every change leaves a trace.

Hosting

Hetzner Cloud; every service follows a standardised, per-service operational layout across the host.

Version Control

Each service — including every venture's site — is versioned in its own private repository under the Nodante GitHub organisation; secrets never enter version control.

Backups & Recovery

Backup archives are consolidated at a single location, with timestamped rollback copies kept for every critical change.

Domains

Every subdomain actively routed at the edge, and the service behind it. Operational interfaces are access-restricted and not intended for public use.

Domain	Service	Description
architecture.nodante.com	static site	The architecture page you are reading now.
nodante.com	static site	Nodante holding's public site — portfolio and contact.
artbr.net	static site	Root site for the artbr brand.
dedekorkut.artbr.net	static site	Product site for Dede Korkut, the story app.
download.artbr.net	media delivery	Direct access to rendered video and published assets.
mail.nodante.com	mail	Mail infrastructure identity; outbound delivery for the holding's mailboxes.
n8n.artbr.net	orchestration	The automation engine's operator interface. Restricted.
live.artbr.net	AI gateway	Live operations dashboard for the AI gateway. Restricted.
prometheus.analytics.artbr.net	metrics	Metrics query interface. Restricted.
dokploy.artbr.net	deployment	Deployment and container management panel. Restricted.

SSH and file-transfer access operate at the protocol level, outside HTTP routing, and are therefore not part of this inventory.

Approach

Own the stack

From domain to deployment, every layer is operated in-house. Fewer dependencies, full control, honest costs.

Automate the routine

Systems watch, heal and publish on their own. Human attention is reserved for building the next thing.

Small, sharp, durable

Ventures stay lean and are built to run for years — measured growth over noise.

Contact

One inbox reaches the root node.

mail@nodante.com