Printora

Diagnostics, maintenance and access for 3D printers with Klipper/Moonraker.

Technologies

Python / FastAPIReactGo

From my Voron to Printora

Restoring and reorganizing my Voron led me to create Printora. I turned that need into software that brings printer information together for diagnosis and maintenance.

Diagnosis close to the printer

Printora combines a diagnosis interface, local API and device-side agent, with integrations for Klipper/Moonraker environments.

What makes up the solution

React/TypeScript system with operation and diagnosis screens that use the API.
View technical details →
Python/FastAPI API for inventory, operations, integrations and local SQLite storage.
View technical details →
Go agent with bounded capabilities to connect the device to application contracts.
View technical details →

Local operation and cloud development Local operation uses SQLite. The cloud layer has PostgreSQL and Redis in development, separate from local printer operation.

My contribution

I created Printora from my work with my Voron printer. I built the interface, local API and agent for diagnosis, maintenance and device access, keeping printer commands out of the browser.

How the system is organized

A backend, frontend and agent connect Klipper/Moonraker printers. Diagnostics and maintenance plans separate reading from execution.

Technical structure

Technology by module.

Web interface, local API and device agent separate experience, storage and printer-environment access.

01 / Existing

System

ReactTypeScriptVite

Operation and diagnosis interface.

Feature-based screens use API contracts without running privileged commands directly from the browser.

02 / Existing

API

PythonFastAPISQLite

API and local storage.

Product inventory, operations and connections, with local SQLite storage. Local operation is separate from the cloud layer.

03 / Existing

Agent

GoCLIsystemdHTTP

Device-side integration.

Runs bounded capabilities and connects the local environment to application contracts.

How the parts connect

The interface communicates with the backend. The agent runs near the device. Klipper, Moonraker and Mainsail integrations have their own contracts and permissions.