PPactDocs
Sales Engineering

Architecture generator

A drag-and-drop architecture canvas that emits a Mermaid diagram and a Pact-branded PDF, with a rule-based architecture suggester and deterministic cost bands — no AI, by design.

The architecture generator turns "here's how Pact fits into your stack" from a whiteboard photo into a shareable, branded artifact. You lay out Pact, the customer's systems, and the integrations between them on a canvas; Pact keeps a diagram and a PDF in sync with it.

The canvas

Drag Pact, tenant systems, and integrations onto the canvas and connect them. On every save, Pact regenerates a Mermaid diagram from the current canvas state and stores it alongside the layout. A live Mermaid render shows you the diagram as you build. Diagram generation is fully deterministic — the same canvas always produces the same diagram.

Branded PDF export

Export any architecture to a Pact-branded PDF to attach to a proposal or walk a prospect through. The document is generated from the same canvas state, so it always matches what's on screen.

Rule-based suggestions — not AI

Pact can suggest an architecture for a tenant of a given shape — vertical, SSO posture, data-residency requirements, and so on. This suggester is a rule-based composer built from codified SE heuristics. It is not an AI feature, and it deliberately does not call a language model.

The suggester is deterministic — it is not AI

The "suggest an architecture" composer is rule-based, built from SE heuristics — no model, no hallucination on architecture, ever. Two tenants of the same shape get the same suggestion. Treat it as an expert-authored template engine, not a generative one.

Deterministic cost bands

Alongside a suggested architecture, Pact produces cost bands — indicative ranges for the shape you described. Like the suggester, these are computed deterministically from codified rules, not estimated by a model. They give a prospect a defensible ballpark without pretending to a precision they don't have.

Versioning

Each architecture carries a monotonic version number that increments as you save, so you can tell which iteration a shared PDF came from.

What's next