Skip to Content
Getting StartedYour First Project

Your First Project

This guide walks you through the core workflow of Quazzar Space: creating a project, organizing it with environments, adding your infrastructure, connecting to a cloud provider, and bringing your team on board.

Step 1: Create a Project

  1. From the dashboard, click New Project
  2. Enter a project name (e.g., “E-Commerce Platform”, “Internal Tools”)
  3. Add an optional description to help team members understand the project scope
  4. Click Create

Your new project opens with an empty workspace ready for environments and infrastructure.

Tip: Most teams create one project per product or major system. If you manage multiple products, create a separate project for each.

Step 2: Set Up Environments

Environments separate your infrastructure by lifecycle stage. A typical setup includes Production, Staging, and Development.

  1. Inside your project, click Add Environment
  2. Enter the environment name (e.g., “Production”)
  3. Optionally add a description and select an icon color for quick visual identification
  4. Click Create
  5. Repeat for additional environments (Staging, Development, QA, etc.)

Each environment has its own set of services, servers, networks, groups, and access controls — so your production infrastructure stays cleanly separated from staging and development.

Step 3: Add Groups (Optional)

Groups help you organize resources within an environment. For example, you might create groups for “Frontend”, “Backend”, “Databases”, and “Infrastructure”.

  1. Open an environment
  2. Click Add Group
  3. Enter a group name and optional description
  4. Click Create

You can also create subgroups within a group for finer-grained organization (e.g., “Backend > Authentication”, “Backend > Payments”).

Step 4: Add Servers

Servers represent the compute resources that host your services — virtual machines, bare-metal servers, or container hosts.

  1. Inside an environment, click Add Server
  2. Fill in the server details:
    • Name — A descriptive identifier (e.g., “api-prod-01”)
    • Provider — Select from AWS, GCP, Azure, Hetzner, OVH, or DigitalOcean
    • Type — Virtual Machine, Bare Metal, or Container
    • Region and Zone — Where the server is physically located
    • Specifications — CPU cores, RAM, disk size
    • Group — Optionally assign to a group
  3. Click Create

Repeat for each server in the environment.

Step 5: Add Services

Services represent the applications and components running on your servers.

  1. Inside an environment, click Add Service
  2. Fill in the service details:
    • Name — The service name (e.g., “User API”, “Payment Gateway”)
    • Type — Web App, API, Database, Queue, Cache, etc.
    • Language — Primary programming language
    • Repository URL — Link to the source code
    • Health Check URL — Endpoint for monitoring (e.g., /health)
    • Server — Assign the service to a server
    • Group — Optionally assign to a group
  3. Click Create

Mapping Dependencies

After adding services, define the connections between them:

  1. Open a service detail page
  2. Click Add Dependency
  3. Select the target service (e.g., “User API” depends on “PostgreSQL Database”)
  4. Choose the connection type (HTTP, gRPC, TCP, Message Queue, etc.)
  5. Click Save

These dependencies appear on the Service Map — an interactive visualization of your entire architecture.

Step 6: Configure Networks

Networks define connectivity between your servers and services.

  1. Inside an environment, go to the Networks tab
  2. Click Add Network
  3. Configure:
    • Name — A descriptive label (e.g., “Production VPC”)
    • CIDR Block — The IP range (e.g., 10.0.0.0/16)
    • VLAN ID — Optional VLAN tag
    • Gateway — Default gateway address
    • DNS Servers — DNS resolver addresses
  4. Click Create
  5. Attach servers and services to the network from their respective detail pages

Step 7: Connect a Cloud Provider

Connecting a cloud account enables auto-discovery of existing resources and real-time cost tracking.

  1. Go to Project Settings > Integrations
  2. Click Add Cloud Account
  3. Select your provider (AWS, GCP, Azure, Hetzner, OVH, or DigitalOcean)
  4. Enter the required credentials:
ProviderCredentials Required
AWSAccess Key ID + Secret Access Key (read-only IAM recommended)
GCPService Account JSON key
AzureTenant ID + Client ID + Client Secret
HetznerAPI Token
OVHApplication Key + Secret + Consumer Key
DigitalOceanPersonal Access Token
  1. Click Connect and Verify

Once connected, you can run Auto-Discovery to scan the cloud account and automatically import servers, networks, and other resources into your project.

Security: All cloud credentials are encrypted at rest. We recommend using read-only credentials with the minimum permissions necessary.

Step 8: Invite Team Members

Bring your team into the project with role-based access control.

  1. Go to Project Settings > Members
  2. Click Invite Member
  3. Enter the team member’s email address
  4. Select their project role:
RolePermissions
OwnerFull access — manage members, environments, billing, and all resources
MemberAccess resources based on environment-level roles
  1. Click Send Invitation

Environment-Level Roles

After a member joins, you can assign more granular roles per environment:

RolePermissions
AdministratorFull control over the environment and all its resources
ManagerCreate, edit, and delete services, servers, and networks
ViewerRead-only access to the environment

Assign environment roles from Environment Settings > Roles.

What to Do Next

With your project set up, explore the features that make Quazzar Space a full infrastructure management platform:

  • Service Map — Open the map view to see your architecture topology and identify dependencies at a glance
  • Cost Estimation — Check the cost dashboard to track spending across all connected cloud accounts
  • Monitoring — Connect Prometheus, Grafana, or Zabbix to get unified alerts in one place
  • Automation — Set up Ansible playbooks in the scheduler to automate routine tasks
  • Import / Export — Back up your environment configuration as JSON for migration or disaster recovery

Further Reading