ZebraByte Cloud Quickstart

This guide walks through the first useful setup in ZebraByte Cloud. ZebraByte is delivered as SaaS, so there is no repository to clone and no Docker or Kubernetes deployment required for customers, advisers or managed-service users.

Before you start

You need:

• access to a ZebraByte Cloud workspace;
• the organization or client you want to manage;
• the framework or regulatory scope you want to begin with;
• at least one person who can own the initial compliance program.

If you want ZebraByte to operate most of the program for you, use Managed Compliance. Professional advisers can follow the same setup for organizations they manage.

Set up your first program

1. Sign in to ZebraByte Cloud

   Use the account and workspace provided during onboarding. The cloud service is operated and updated by ZebraByte; you do not need to provision application infrastructure.

2. Create or select an organization

   An organization is the top-level boundary for compliance data, members, frameworks, risks, vendors, policies, evidence and audits.

   Advisers working with multiple companies should keep each client in the appropriate organization boundary so records and access remain separated.

3. Add the people who need access

   Invite the internal owners, compliance team or professional advisers who will participate in the program. Configure roles according to the responsibilities each person actually needs.

4. Choose the first framework

   Select the framework relevant to the organization’s goal—for example SOC 2, ISO 27001 or another supported compliance scope. Start with the requirement that creates the most immediate regulatory, assurance or commercial value.

5. Review controls and ownership

   Map controls to the security and operational practices already in place. Assign owners and identify the areas where evidence or remediation is still required.

6. Connect evidence and integrations

   Use supported integrations and platform workflows to gather evidence from the systems the organization already operates. Manual evidence can be added where automation is not appropriate.

7. Build the risk and policy baseline

   Record material risks, link safeguards and establish the controlled documents required for the chosen framework. Policies should reflect how the organization actually works rather than exist only for an audit.

8. Track readiness continuously

   Use tasks, findings, evidence status and recurring reviews to keep the program current. Audit preparation should come from the live compliance system rather than a separate last-minute document project.

Which delivery model are you using?

Self-service Cloud Your company operates the compliance program directly in ZebraByte Cloud

Professional / adviser Use the same cloud platform as the operating environment for compliance work delivered to client organizations

Managed Compliance ZebraByte specialists take on more of the controls, evidence, remediation and audit-readiness workload

Developer integrations Automate workflows through GraphQL, CLI, MCP, n8n and webhooks

Architecture reference

The documentation still includes Docker Compose and Kubernetes pages inherited from the platform’s deployment lineage. They are preserved for architecture analysis and migration reference, but they are not ZebraByte installation instructions and ZebraByte is not distributed as open-source/self-hosted software.

If you are evaluating a migration from an earlier deployment model, start with the architecture reference.