Documentation overview

This documentation describes Prismelo as a company, how our services are scoped and delivered, and the technical conventions behind the systems we build.

It is written for three audiences: clients evaluating or working with us, engineers integrating with our work, and anyone maintaining a system we have handed over.

How this documentation is organised

• Getting started covers the practical shape of an engagement — how work begins, how it is scoped and how communication runs.
• Company information holds the facts about Prismelo: what the company is, how the brand is used, and where legal policies live.
• Services documents each service area and the rules that apply to security work.
• Products covers companies and products operated within the Prismelo group.
• Technical guides are implementation notes for engineers working on Prismelo-built systems.
• FAQs answers the questions that come up most often before an engagement.

Status labels

Every page carries a status. Most are Published and describe current practice. A page marked Placeholder exists to hold a defined place in the structure while the underlying detail is still being confirmed — it will say so at the top of the article.

Conventions used here

Command examples assume a POSIX shell. Code samples are written in TypeScript unless a different language is stated. Field names appearing in examples — environment variables, request bodies — match the implementation in this website's repository.

A note on security documentation

Testing methodology, internal runbooks and client-specific architecture are not published on the open web. Those documents are shared within an engagement, under confidentiality terms where required. The responsible disclosure page explains how to report a security issue.

Getting help

For anything not covered here, contact Prismelo or email hello@prismelo.tech. Documentation corrections are genuinely welcome — if a page is wrong or unclear, tell us which one.