LaserData Cloud

Introduction

Deploy and operate Apache Iggy through LaserData Cloud, your cloud account, or your own infrastructure

Start with your first Free deployment. The guide covers signup, readiness, credentials, and your first messages, with Docker and native SDK paths.

Early Access

LaserData Cloud is publicly available. Sign up at laserdata.cloud to create a Free tier deployment on AWS or GCP. No credit card is required. Free deployments use one node on shared infrastructure. Paid deployments use three nodes with replication between nodes.

APIs and behavior can change during this initial launch. Read more at laserdata.com. Send questions to [email protected].

LaserData Cloud deploys and operates Apache Iggy, a persistent message streaming platform written in Rust. It manages infrastructure, upgrades, networking, and security. Choose Managed, Bring Your Own Cloud (BYOC), or On-Premise according to where your infrastructure must run.

Before You Sign Up

Sign in with GitHub, Google, or Microsoft. The Console does not offer a separate email-and-password account. The profile form requests your name, Title / Position, an organization name when creating a workspace, and acceptance of the terms. For personal use, enter Student or Hobbyist as your title and a name for your project as the organization.

The first eligible organization can create one Free deployment without a credit card. It uses one isolated slot on a shared host. Read the current Free limits before choosing it. A Pro organization badge does not turn a Free deployment into a paid deployment.

Provisioning runs in the background. Wait for the deployment to become initialized, then follow the connection steps. Setup time varies with available capacity and node startup. A disabled Stream UI button does not prevent you from reading the guide.

Why LaserData Cloud

Iggy supports TCP, QUIC, HTTP, and WebSocket. Performance depends on hardware, message size, batching, replication, and network distance. Benchmark figures for Iggy are not Free-tier throughput or latency promises. LaserData Cloud adds the services that operate it:

  • Create infrastructure, install upgrades, manage TLS certificates, and monitor deployments.
  • Use Managed, BYOC, or On-Premise deployments through the same interface.
  • Use Laser SDK from Rust, Python, or TypeScript. One connection supports streaming, views, state, graph, memory, context, and agent fabric, the services that coordinate agents.
  • Manage resources through the Web Console or laser, the command-line tool. Its TUI dashboard provides an interactive terminal interface.
  • Control access with outbound management connections, signed tasks, scoped credentials, and client access rules.
  • Organize resources into Organizations, Divisions, Environments, and Deployments. APIs call an organization a tenant. Roles assign permissions at each level.
  • Read telemetry dashboards, audit logs, and current health reports.
  • Choose Standard, Performance, or Enterprise. Pricing starts from $199, $999, and $2,999 per month on AWS. Compute and Storage form the configuration price, with data transfer billed separately for actual usage.
  • Protect data with TLS, disk encryption, and optional custom key encryption. Immutable audit logs, GDPR data export, and deletion support compliance requirements.

How You Manage It

The Console and laser CLI use the same APIs, authentication, and permission model. Both manage deployments, connectors, networking, telemetry, audit logs, and organization resources.

The CLI is a single static binary for macOS and Linux. Use commands such as laser deployment list -o json in scripts, CI, and agents. Run laser tui to open the interactive dashboard.

Install the CLI:

curl -fsSL https://cli.laserdata.cloud/install.sh | sh

The REST API exposes every deployment and organization operation. The CLI includes tier selection and pricing previews for paid deployments.

Deployment Models

ModelInfrastructureData LocationBest For
ManagedLaserData AWS/GCPLaserData AWS/GCPFully managed, no infrastructure setup required
Bring Your Own Cloud (BYOC)Your AWS/GCP accountYour AWS/GCP accountEnterprises needing data sovereignty
On-PremiseYour infrastructureYour infrastructureRegulated industries and private infrastructure with outbound control-plane access

All three models use the same Warden agent, Console UI, and APIs. Warden is the agent that manages each node. The model determines where the infrastructure and data reside.

Architecture at a Glance

ComponentRoleCommunication
Console UIWeb interface for managing deploymentsTalks to Platform API
Platform APICentral control planeReceives connections from Warden
Warden AgentLightweight agent on each nodeOutbound HTTPS only - pulls config, tasks, and certs
Iggy ServerMessage streaming platformManaged by Warden on each node

Warden starts each management connection from the node to the control plane, the services that manage deployments. These connections use outbound HTTPS. The control plane does not use inbound connections, SSH, or SSM to manage your infrastructure.

On this page