Printora

Software for 3D printer diagnostics.

Identified technologies

Python / FastAPIReactGo

The problem

Reading a 3D printer’s state and acting on it are different tasks. The interface must show information without running privileged commands in the browser.

The solution

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 →

Project scope The local system uses SQLite. PostgreSQL and Redis belong to cloud work in progress, separate from the local operation shown here.

My contribution

I designed and developed Printora, with a web interface, local API and device agent. The architecture separates diagnosis, maintenance planning and device-side actions.

Architecture overview

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.

What each part does and which technologies support it. A module in the code does not mean all its features are complete or published.

01 / Existing code

System

ReactTypeScriptVite

Operation and diagnosis interface.

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

02 / Existing code

API

PythonFastAPISQLite

API and local storage.

Organizes inventory, operations and integrations. The local scope uses SQLite and does not depend on the cloud design.

03 / Existing code

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.

Data and integrations

SQLite supports local operation. PostgreSQL/Redis belong to cloud work in progress and are not shown as replacements for local storage.

Quality and operations

Separate frontend, backend and agent checks, conservative device integration and local installation/rollback steps. UI tests do not replace physical acceptance.