Architecture
Architecture & Technical Documentation
Explore how Pledger.io is designed, how core processes work, and how the API is structured.

Technical documentation

Technical documentation of Pledger.io

This section is intended for contributors, integrators, and operators who want to understand how the platform is built and why specific design decisions were made.

Pledger.io is implemented as a modular monolith with clear module boundaries, explicit domain modeling, and a contract-first REST API.

Architectural design of the project

Structural design of Pledger.io across domain, backend, UI, and deployment.

Business processes modeled

Technical process flows and runtime behavior in Pledger.io.

Architecture Decision Records

Key technical decisions and trade-offs in Pledger.io.

REST API documentation

Browse the Pledger.io REST API below. Endpoints are grouped by tag; expand Schemas in the sidebar to inspect request and response entities. Authentication uses a bearer JWT unless an operation is marked as public. The machine-readable specification is also available as OpenAPI YAML.

Browse release notes for version history and downloads.

If you are new to the codebase, start with Design and Backend Design. Then continue with Process to understand runtime flows, and finish with the Architecture Decision Records for historical context.

Last modified on July 4, 2026 Edit this page on GitHub