Standardoc — Document Format Standardizer

From ~3 hours to ~30 seconds. Upload a document, download a perfectly formatted version that matches your company template — fast, consistent, and local.
Tech Stack: Next.js TypeScript PostgreSQL Keycloak MinIO Docker Hasura Hetzner

Standardoc — Document Format Standardizer

The boring tool that saves hours of manual document formatting.

Overview

Standardoc automates document standardization across an organization. Convert PDFs, Word, Excel, PowerPoint, or text-based files into company‑template‑compliant documents — quickly and consistently.

  • From ~3 hours manually to ~30 seconds with Standardoc
  • Client-side text/data transforms run in seconds
  • Server-side PDF processing averages ~2.3 seconds in local tests

Problem

Manual formatting is slow, inconsistent, and risks compliance. Teams routinely burn hours per document cleaning layouts, headings, spacing, and branding.

Solution

Upload a document → 30 seconds later, download a perfectly formatted version that uses your existing templates and brand rules. No workflow changes.

How It Works

  1. Upload one or many documents
  2. Select a company template
  3. Download standardized files

Capabilities

  • Bulk processing (single or hundreds)
  • Template engine (reusable, company-defined)
  • Multi-format support: PDF, DOCX, XLSX, PPTX, MD/TXT/CSV/JSON/HTML/XML
  • Local-first: runs in your environment with your identity/storage

Technical Overview

  • Web/API: Next.js (TypeScript)
  • Database: PostgreSQL (Docker)
  • Identity: Keycloak (Docker)
  • Storage: MinIO (Docker)
  • Optional: Hasura (GraphQL), OpenObserve (observability)
  • Deploy: Docker Compose; production-ready behind HTTPS/Reverse Proxy
  • License: Proprietary (EULA)

Role & Contributions

  • Led architecture and implementation (Next.js + Dockerized services)
  • Built document processing pipeline and template engine
  • Integrated authentication/authorization with Keycloak
  • Provisioned Postgres/MinIO; added observability hooks
  • Established CI/CD practices and operational runbooks

Why It Works

  • Simple, focused scope (one job done well)
  • Direct ROI: “3 hours → 30 seconds”
  • Minimal change friction: use your existing templates; no retraining

Outcomes

  • Measured reduction from hours to seconds per document
  • Server-side PDF processing ~2.3s average (local tests)
  • Pilot usage across teams; simplified codebase and operations
  • Clear path to enterprise features (teams, SSO, API expansion)

Contact

  • Maintainer: Repository owner
  • Inquiries: see repo profile or projectUrl above
automation document-management productivity api-integration enterprise