> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cyberwave.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Support

> How to get help with Cyberwave — community, GitHub, FAQs, and direct contact.

Cyberwave is built in the open with a small, responsive team and a growing community. This page is the single place to figure out **where to go when you need help** — whether you're stuck on a quickstart, hit a bug, or want to talk to a human.

***

## Where to get help

<CardGroup cols={2}>
  <Card title="Discord community" icon="discord" href="https://discord.gg/dfGhNrawyF">
    The fastest place to ask a question, share what you're building, or get
    unstuck. The team and other builders hang out here every day.
  </Card>

  <Card title="GitHub issues" icon="github" href="https://github.com/cyberwave-os">
    Found a bug or want to request a feature? Open an issue on the relevant repo
    under the [`cyberwave-os`](https://github.com/cyberwave-os) organization
    (SDKs, CLIs, drivers, edge components, this docs site).
  </Card>

  <Card title="Contact us" icon="envelope" href="https://cyberwave.com/contact-us">
    For sales, partnerships, on-premises deployments, or anything that doesn't
    belong in a public channel, reach out directly.
  </Card>

  <Card title="Platform status" icon="signal-bars" href="https://status.cyberwave.com">
    Live uptime for the API, MQTT broker, and app. Check here first — if
    something is down, it's probably not your code.
  </Card>

  <Card title="Changelog" icon="clock-rotate-left" href="/changelog">
    Check what shipped recently and whether a recent change might explain what
    you're seeing.
  </Card>
</CardGroup>

<Tip>
  Not sure which channel to use? Default to **Discord** for questions and
  **GitHub issues** for reproducible bugs or feature requests.
</Tip>

***

## Filing a good GitHub issue

A reproducible report gets fixed dramatically faster. When opening an issue on a [`cyberwave-os`](https://github.com/cyberwave-os) repo, please include:

* **What you ran**: the command, code snippet, or UI action.
* **What you expected** vs. **what happened** (include the full error or log output).
* **Environment**: OS, Python / Node version, SDK or CLI version, and whether you're on cloud or self-hosted.
* **Catalog item** (if relevant): the asset, model, or driver slug — e.g. `the-robot-studio/so101`, `unitree/go2`.
* A **minimal reproduction** if you can — even a 10-line script helps.

Pick the repo closest to where the issue lives (Python SDK, CLI, a specific edge driver, the docs, etc.). If you're not sure, ask on Discord first and we'll point you at the right place.

***

## Catalog-item help (robots, models, datasets)

Most "how do I…" or "why isn't this working" questions about a **specific** catalog item are answered on that item's own page rather than here. Every catalog entry has its own setup guide, capabilities reference, and item-specific troubleshooting.

Start there before opening a general issue:

<CardGroup cols={2}>
  <Card title="Robot hardware" icon="robot" href="/overview/supported-hardware">
    Per-robot setup, supported features, calibration tips, and known issues for
    each supported arm, mobile base, quadruped, and drone.
  </Card>

  <Card title="Model catalog" icon="brain" href="/feature-reference/ml-models">
    Per-model usage, supported inputs/outputs, training notes, and gotchas for
    each model in the catalog.
  </Card>

  <Card title="Asset catalog" icon="book-bookmark" href="/feature-reference/catalog">
    How catalog assets, registry IDs, and slugs work — and how to upload your
    own.
  </Card>

  <Card title="Datasets & recordings" icon="database" href="/feature-reference/environment-editor/replay">
    How datasets are generated from recordings, supported formats, and
    import/export options.
  </Card>
</CardGroup>

<Info>
  **Rule of thumb:** if your question starts with "for the SO-101…" / "for Go2…"
  / "for SmolVLA…", the answer is most likely on that item's page. This Support
  page covers cross-cutting questions about the platform itself.
</Info>

***

## FAQs

A growing list of frequently asked questions about the platform as a whole. For item-specific questions, see the catalog links above.

### General

<AccordionGroup>
  <Accordion title="What is Cyberwave?">
    Cyberwave turns every robot and sensor into a digital twin that your code, your models and your agents can drive, with the same API in simulation and on real hardware. See [Connect AI to robots](/ai/overview).
  </Accordion>

  <Accordion title="How does Cyberwave compare to a traditional simulator?">
    A simulator models a robot. A Cyberwave twin is the same object in simulation and on the real robot: `cw.affect("simulation")` or `cw.affect("live")` switches
    which one your code drives. See [What is a digital twin](/overview/features/digital-twin) and [Simulation](/overview/features/simulation).
  </Accordion>

  <Accordion title="Do I need hardware to get started?">
    No. [Develop in simulation](/overview/hello-robot) runs in the browser with no code, and [Your first AI loop](/overview/first-ai-loop) needs only a
    laptop webcam. To drive a real arm without owning one, see [Develop with remote hardware](/overview/develop-remote-hardware).
  </Accordion>

  <Accordion title="Is there a free tier?">
    Playground simulation is free. MuJoCo simulations, AI usage, platform events and storage use credits. See [Credits & Billing](/billing/credits).
  </Accordion>
</AccordionGroup>

### Accounts, workspaces & pricing

<AccordionGroup>
  <Accordion title="What is a workspace?">
    A workspace is your team's container for environments, workflows and resources, with its own members, permissions and billing. See [Data model](/feature-reference/architecture/core-data-hierarchy).
  </Accordion>

  <Accordion title="How do I invite teammates?">
    Share a project from its settings: click **Share**, add people by email and pick a role. See [Access control](/feature-reference/access-control).
  </Accordion>

  <Accordion title="How is usage billed?">
    In credits. Platform events, AI usage and storage are metered, and a MuJoCo simulation costs about 0.6 credits per hour. The Usage page in your organization settings shows rates and charges. See [Credits & Billing](/billing/credits).
  </Accordion>

  <Accordion title="Can I use Cyberwave on-premises?">
    A self-hosted package exists; contact Cyberwave. Air-gapped deployment is not available as a packaged option. See [Cyberwave for integrators](/enterprise/overview#deployment-options).
  </Accordion>
</AccordionGroup>

### Hardware compatibility

<AccordionGroup>
  <Accordion title="Which robots are officially supported?">
    See [Supported hardware](/overview/supported-hardware) for the compatibility table and the [catalog](https://cyberwave.com/catalog) for every device.
  </Accordion>

  <Accordion title="Can I integrate a custom robot?">
    Yes. Create an asset from its URDF and write a driver. See [Add your robot](/robots/add-your-robot), [custom
    hardware](/overview/connecting-hardware/custom-hardware) and [writing compatible
    drivers](/feature-reference/edge/drivers/writing-compatible-drivers).
  </Accordion>

  <Accordion title="Which cameras and sensors are supported?">
    USB, RTSP, GigE and RealSense cameras, plus [cameras](https://cyberwave.com/cyberwave/standard-cam),
    [microphones](https://cyberwave.com/catalog/tag/microphone), and other sensors.
  </Accordion>

  <Accordion title="Does Cyberwave support ROS 2?">
    Yes. Drivers can be ROS 2 nodes built on [BaseROS2Driver](/feature-reference/edge/drivers/ros2-base-driver). See [Supported hardware](/overview/supported-hardware).
  </Accordion>
</AccordionGroup>

### SDKs & integrations

<AccordionGroup>
  <Accordion title="Which SDKs are available?">
    The [Python SDK](/overview/tools/python-sdk), [C++ SDK](/overview/tools/cpp-sdk), [MCP server](/overview/tools/mcp-server), and [Claude Skill](/overview/tools/claude-skill).
  </Accordion>

  <Accordion title="How do I authenticate the SDK?">
    Create a token under **Profile → Access** and export it as `CYBERWAVE_API_KEY`. See [API tokens](/feature-reference/api-tokens) and
    [Authentication](/feature-reference/setup-cyberwave).
  </Accordion>

  <Accordion title="Can I use Cyberwave from Cursor or Claude?">
    Yes. Point your client at the hosted MCP server, `https://mcp.cyberwave.com/mcp`, with your API key as a Bearer token. See the [MCP
    server](/overview/tools/mcp-server).
  </Accordion>

  <Accordion title="What languages does the REST API support?">
    Any language with an HTTP client. Send `Authorization: Bearer <api-key>` to `https://api.cyberwave.com`. See the [API overview](/api-reference/overview).
  </Accordion>
</AccordionGroup>

### Edge & deployment

<AccordionGroup>
  <Accordion title="What is Cyberwave Edge?">
    Edge Core runs on the computer next to your robot. It registers the device and runs drivers and workers as Docker containers. See [Edge runtime](/feature-reference/edge/overview).
  </Accordion>

  <Accordion title="What hardware can run an Edge node?">
    Raspberry Pi, Jetson, x86 Linux machines and macOS. See [Raspberry Pi](/feature-reference/edge/raspberry-pi) and
    [Jetson Orin Nano](/feature-reference/edge/jetson-orin-nano).
  </Accordion>

  <Accordion title="Can Edge nodes run offline?">
    Offline behaviour is not documented yet. Edge nodes need outbound access to `api.cyberwave.com` and `mqtt.cyberwave.com`; see [Network and firewall requirements](/enterprise/network-and-firewall), and ask on [Discord](https://discord.gg/dfGhNrawyF) for details.
  </Accordion>

  <Accordion title="How do I write a custom driver?">
    Subclass the SDK's driver base class and declare its interface. See [Writing compatible drivers](/feature-reference/edge/drivers/writing-compatible-drivers).
  </Accordion>
</AccordionGroup>

### AI models, workflows & datasets

<AccordionGroup>
  <Accordion title="Can I bring my own model?">
    Yes, in early access: call your own API or hand Cyberwave code to run. See [Bring your own model](/feature-reference/ml-models/uploading-your-model).
  </Accordion>

  <Accordion title="What model formats are supported?">
    On the edge, workers run Ultralytics (`.pt`), ONNX Runtime, TFLite and OpenCV models, each behind an SDK extra (`ml`, `ml-onnx`, `ml-tflite`, `ml-opencv`). See [Model cache](/feature-reference/workflows/workers/model-cache).
  </Accordion>

  <Accordion title="How do I build a workflow?">
    Wire triggers, models, conditions and robot commands on the visual canvas, or ask the [workflow assistant](/ai/workflow-assistant). See [Build and run
    workflows](/feature-reference/workflows).
  </Accordion>

  <Accordion title="How are datasets generated?">
    From [recordings](/feature-reference/environment-editor/replay) of your twins, or by [importing](/feature-reference/datasets/import) from Hugging Face Hub or a zip file.
  </Accordion>
</AccordionGroup>

### Teleoperation & streaming

<AccordionGroup>
  <Accordion title="What latency can I expect?">
    Latency figures are not published yet. See [Live Teleoperation](/feature-reference/environment-editor/teleoperation).
  </Accordion>

  <Accordion title="Does teleoperation work behind a corporate firewall?">
    Usually, yes. Every connection is outbound, and video relays over TLS on port 443. See [Network and firewall requirements](/enterprise/network-and-firewall).
  </Accordion>

  <Accordion title="Which browsers are supported?">
    Not documented yet. [Contact us](https://cyberwave.com/contact-us) if you need a specific browser.
  </Accordion>
</AccordionGroup>

### Security & data

<AccordionGroup>
  <Accordion title="Where is my data stored?">
    Hosting regions and retention are not documented yet. [Contact us](https://cyberwave.com/contact-us).
  </Accordion>

  <Accordion title="How is data encrypted?">
    In transit, REST uses HTTPS, MQTT uses TLS on port 8883, and the video relay uses TLS on port 443. For encryption at rest, [contact us](https://cyberwave.com/contact-us).
  </Accordion>

  <Accordion title="Who can access my workspace data?">
    Workspace members, according to their roles, people you share a project with, and anyone with a project's public link. See [access
    control](/feature-reference/access-control).
  </Accordion>

  <Accordion title="Is Cyberwave compliant with SOC 2 / GDPR / HIPAA?">
    Ask us. [Contact us](https://cyberwave.com/contact-us) for current certifications.
  </Accordion>
</AccordionGroup>

***

## Still stuck?

If none of the above unblocks you:

1. Check [platform status](https://status.cyberwave.com) — confirm whether it's us before you debug it.
2. Search the [`cyberwave-os` GitHub org](https://github.com/cyberwave-os) for an existing issue.
3. Ask in [Discord](https://discord.gg/dfGhNrawyF) — usually the fastest path to an answer.
4. [Open a new GitHub issue](https://github.com/cyberwave-os) on the relevant repo with the details from the [filing a good issue](#filing-a-good-github-issue) checklist above.
5. For private or commercial questions, [contact us](https://cyberwave.com/contact-us) directly.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.