Loading…
Loading…
GlobiGuard helps teams review data, apply policy checks, and keep records around supported AI workflows. Public tools are open for exploration, but the main product path starts with an account and the workspace at /app.
The hosted product is organized around the workspace in /app. That is where teams review access, billing, app setup, and approval activity.
Public tools such as the PII playground and model compare stay available for exploration, but they are no longer the canonical onboarding surface for the product itself.
Start from the product auth flow, then enter the workspace at /app. This is the primary onboarding path for the hosted product.
Use the workspace overview to confirm access, billing state, and what needs to be set up next.
Bring at least one provider and one product path online. Model-provider setup is documented here, while some connector rollouts still need guided setup.
Learn moreIf your rollout uses the public libraries, start with the libraries page to pick the right package and runtime boundary before wiring credentials.
Learn moreSet up app records, create browser or server keys, and prepare deployment files when your rollout needs them.
Learn moreKeep the public docs nearby for setup guidance, and use the trust page when you need a public security or deployment overview.
Learn moreChoose the right package and install the canonical SDK, React, contracts, or n8n surface.
Review supported providers, key formats, and deployment-aware setup expectations.
Read the public trust notes, deployment boundaries, and review paths.
Request customer-specific questionnaires, architecture review, or rollout help.
Product integrations should be provisioned from the authenticated workspace path or the package docs, not older demo-only flows. Use the runtime/install surfaces in /app, the package guide in /docs/libraries, the public setup guides in /docs/*, and the machine-readable summary at /llms.txt.