Where responsibility will sit.

Infrastructure you pay for

The platform will create infrastructure on your cloud or hypervisor account, under credentials you grant it. The resulting bill is yours, including when a deployment turns out larger or longer-lived than intended.

We intend to state plainly that FMJ Consulting is not liable for infrastructure costs incurred through the platform. We would rather set that expectation before you connect an account than argue about it afterwards.

Deployments apply automatically

This is the term we would most want a prospective customer to read twice.

The platform plays each infrastructure change automatically once its plan succeeds. There is no manual approval step between deciding to deploy and the change being applied — and that includes changes that destroy infrastructure. Deleting a project removes what was provisioned for it.

This is a deliberate design choice, made so the platform is a delivery tool rather than a ticket queue. The terms will therefore be explicit about it, and the liability position will reflect it honestly rather than relying on a cap that would be hard to defend after a destructive change.

Access tokens and credentials

• You grant the platform tokens and credentials that reach your systems, and you retain ownership of them: issuing, scoping, rotating and revoking are yours.
• Grant the narrowest scope that works. The platform is designed to need a project-restricted credential rather than an account-wide one.
• Stored credentials are encrypted at rest. The data processing page describes what that protects against, and what it does not.

Templates and golden paths are provided as-is

The component catalog, deployment templates and pipeline configuration are starting points, versioned and pinned so they behave predictably. They are not certified against any particular regulatory or internal security regime, and we do not intend to warrant that they are. Reviewing them against your own compliance requirements stays with you.

Plans and downgrades

Your plan sets what you can create: how many projects, how many components. Upgrading raises those quotas and changes nothing else.

Downgrading deletes. If you move to a smaller plan while projects exist, the platform tells you so and asks once; accepting deletes your projects and the infrastructure deployed for them, through the same automated teardown the platform always uses. There is no partial survival and no selection step — the simplicity is deliberate, and this paragraph is the document the confirmation dialog names.

Limits of liability

A single flat cap covering everything equally is the industry norm and, for this product, not an honest one: software that changes infrastructure without a human gate can cause harm out of proportion to a monthly fee. The intended position is a general cap with a higher, separate limit for infrastructure destruction and data loss, rather than pretending the two risks are the same size.

The final wording is for counsel. We are recording the principle now so it is designed in rather than negotiated late.