Technology · Stack

The verified production stack.

This is our first verified production standard: every layer below runs in a live Renaix system today. It is a standard, not a fixed bundle; technology is selected for each system's workflow, security, data, and operating requirements.

Cloud infrastructure
Hetzner
Renaix responsibility

Provisioning, deployment environment, service operation

Containerized deployment
Docker, Docker Compose
Renaix responsibility

Reproducible services, isolation, versioned deployment recipes

TLS and routing
Caddy
Renaix responsibility

Secure endpoints, controlled public exposure

Workflow orchestration
n8n
Renaix responsibility

Ingestion, extraction, matching, human review, scheduling, error workflows

Operational source of truth
PostgreSQL
Renaix responsibility

Schema design, reconciliation state, evidence, exceptions, role-scoped views

Deterministic processing
SQL, version-controlled Node.js
Renaix responsibility

Testable normalization, matching, validation, and export logic

AI extraction and reasoning
Anthropic Claude API
Renaix responsibility

Model integration, structured extraction, tool use, refusals, evaluation

Agent runtime
Node.js, TypeScript
Renaix responsibility

Domain-agent services, authentication, query logging, rate limits

Agent interoperability
Model Context Protocol
Renaix responsibility

One secure, versioned, revocable endpoint per domain agent

Validation and testing
Zod, TypeScript, automated tests, evaluation sets
Renaix responsibility

Input and output validation, security and regression testing, acceptance gates

User interfaces
Claude and MCP-compatible clients
Renaix responsibility

Secure connection of approved users to role-scoped agents

Source and deployment control
Git, GitHub
Renaix responsibility

Reviewable code, workflow definitions, deployment recipes, change history

Hosted model inference is provided by the model vendor; Renaix owns the integration, prompts, tools, evaluations, credentials, and operating lifecycle. Model-agnosticism is a design principle: the architecture allows the model layer to change without the business losing its data, controls, or workflows.