Architecture + AIPanagiotis Koletsos

Promptrilla | Hosted project

Prompt management with version history, retrieval, and real production boundaries.

Promptrilla is a multi-tenant prompt workspace for people who need more than chat history and ad hoc notes. It turns prompts into versioned assets with tagging, search, team workflows, and a production runtime that treats isolation, deployment, and operations as part of the product.

Open live productView repository

Project snapshot

Use the snapshot to understand scope, build posture, and current focus quickly.

This section stays compact on purpose so both product pages and deeper technical builds can start with the same fast read.

Product posture

Cloud-native multi-tenant web product, not a local prompt notebook.

Core stack

FastAPI backend, React 18 frontend, Supabase Auth and PostgreSQL, optional Pinecone search.

Isolation model

Per-request user-scoped Supabase access with Row-Level Security enforcing tenant boundaries.

Production shape

Same-origin runtime on K3s with GHCR images, semver releases, and Flux promotion.

Build story

Follow the project through a small number of deliberate chapters.

Each chapter can lean more product-first or more systems-first, but the route structure stays stable across both.

Why it matters

Promptrilla supports the broader profile because it proves product judgment, not only implementation speed.

The value of the page is the combination of UX, tenancy design, delivery workflow, and operational readiness. It shows the same architecture thinking in a product context that the rest of the site shows in enterprise work.

It connects AI-era tooling needs with real user, team, and deployment constraints.
It demonstrates full-stack ownership across data, auth, UI, hosting, and release flow.
It makes architecture decisions legible through a live system instead of only through diagrams or claims.
Product angle

Chat history is not a durable prompt system.

The product starts from a practical problem: once prompts become useful assets, copy-paste notes and scattered chats stop being enough. The page needs to show Promptrilla as a real workspace, not a thin demo around a text box.

  • Prompt assets can be stored, versioned, tagged, and revisited instead of disappearing into chat logs.
  • The workflow supports both private libraries and shared team use without losing authorship context.
  • Search and metadata make retrieval part of the product rather than an afterthought.
  • The product is shaped for repeat use, not one-off prompt experiments.
Architecture

The technical story is about isolation, explicit boundaries, and upgradeable infrastructure.

Promptrilla is intentionally split into a backend API, a frontend SPA, managed auth and database boundaries, and optional semantic search. That makes the architecture visible in the product instead of hidden behind a single repo label.

  • FastAPI owns the auth-aware API surface, CRUD flows, health endpoints, and integration points.
  • React and TypeScript carry the authenticated product surface and workflow navigation.
  • Supabase Auth and PostgreSQL RLS enforce tenant isolation as a system rule, not a UI promise.
  • Pinecone stays optional so semantic search can be layered on without becoming the system of record.
Runtime

The page is not only about code quality; it is about a real release and hosting path.

The project already runs under a public product URL with same-origin API routing, GitHub-driven releases, and GitOps promotion. That makes it stronger portfolio proof than a repo-only concept.

  • Production runs on K3s on the Intel NUC with Flux reconciliation and public GHCR images.
  • Semver tags publish release artifacts and drive production promotion instead of raw pushes to main.
  • The product supports both subdomain hosting and future path-prefix hosting through explicit base-path configuration.
  • Open self-signup and branded auth flows make the runtime usable as a real product surface.

Proof points

Public proof beyond the headline

The strongest signal is that Promptrilla combines product shape, technical boundaries, and a real operational path instead of stopping at a prototype.

User-facing scope

Prompt management, safe editing, version history, metadata, search, workspace flows, and AI-assist surfaces.

Test posture

README-documented coverage across backend pytest, frontend Vitest, and Playwright smoke runs.

Deployment discipline

Semver releases publish GHCR images and Flux promotes production automatically.

Live runtime

Public product URL with same-origin API routing and base-path hosting support for future migration.

Next routes

Use the live links, repo, and related site routes next.

Hosted project pages should be able to point both outside the site and back into the broader proof system without requiring a different route pattern per project.

LiveRepo

Continue in the site

Back to Selected WorkContact and profiles