Questions people ask first

Cost, keys, licensing, upstream, and when you can actually download it.

When can I download it?

Not yet. The panel works, but it is not packaged for public download — there are no installers to hand you. Rather than publish a link that 404s, there is a waitlist: leave an email and you get one message on the day builds go live.

What does it cost?

The panel is free and open source under AGPL-3.0. There is no paid tier today.

If paid features arrive later, they will be additions, not a paywall dropped over what already works. The panel stays open source.

The costs that matter are the ones GambaOS helps you see: what your model providers charge you. GambaOS never touches that money — you pay your providers directly.

Do you get my API keys?

No. Keys stay in your own configuration, on your own machine. The panel reads them to talk to the providers you configured, and that is the whole story. There is no GambaOS server for them to be sent to.

If you would rather verify than trust, the source is public and this is exactly the kind of claim worth checking yourself.

Does it phone home?

Once, for updates: the app asks gambaos.com whether a newer version exists.

The analytics inherited from the upstream project were deleted from the source, not hidden behind a setting. There is no usage telemetry.

Is this the same as ClawPanel?

It started as a fork of it. It is now maintained independently, with the security audit, cost guard, and a fair amount of other work added, and the upstream’s telemetry and revenue placements removed.

Both are AGPL-3.0. GambaOS does not speak for the upstream project, and the upstream does not speak for GambaOS.

Does it work with OpenClaw and Hermes at once?

Yes — that is the point of the panel. Models, channels, sessions, logs and scheduled tasks are managed the same way for either runtime, so switching engines does not mean relearning your tools.

Can I run it on a server instead of my laptop?

Yes. There is a web version intended for a VPS, so you can manage agents from a browser. Treat it as you would any admin panel: put it behind authentication and do not expose it to the open internet. The security audit will tell you if you did.

What is the AGPL going to require of me?

If you run it for yourself, nothing beyond keeping the licence intact. If you modify it and offer it to other people over a network, the AGPL requires you to make your modified source available to them. Running a private instance for your own use does not trigger that.

This is a summary, not legal advice — the licence text in the repository is what actually governs.