About

Two pages that answer "should I trust this?" and "does this actually exist yet?" — the questions that don't belong in a task guide but decide whether a guide is worth following.

The pages

• Security & disclosure — how to report a vulnerability, what AppGantry does to protect accounts and artifacts, the identifiers to check before you consent to anything, and where security.txt lives.
• Feature availability — what is gated by plan, what is gated by environment, what is assisted rather than self-serve, what has not shipped, and what is deliberately unpublished. It is also the canonical list of the controls that exist only on the API.

Read Feature availability first when

• a screen these docs describe isn't in your web app;
• an operation is refused and you can't tell whether it's your role, your plan, or the feature;
• you're about to build automation against something and want to know whether it works today. Store publishing does not — a job is created and then fails, on every plan, for every provider; and
• you're wondering whether a behaviour is contractual or merely current.

Read Security & disclosure first when

• you have found something and need the disclosure address and expectations;
• you are about to admin-consent AppGantry's application into your Azure tenant and want to verify the identifiers independently; or
• somebody has asked you how artifacts, credentials, and audit records are protected.

See also

• Plans & pricing: what each plan includes.
• Rate limits: the thresholds that are published and the ones that aren't.
• FAQ: the short-answer version of much of this.