Haptique OS beta is live now

[ccsfounder]

Haptique Beta is live. It arrived.

The first Haptique OS Beta is now live for the community.
This beta brings three major pieces together:

1. Haptique OS

Haptique OS is the new local runtime for Haptique.

It runs on your own machine and gives you a local control layer for devices, automation, integrations, and the Haptique experience without depending on a remote cloud server for day-to-day operation.

2. Local Fleet Server

This beta also includes the local Fleet Server path.

That means the configuration apps and Haptique RS90 can communicate with your own local Haptique server instead of relying on the current hosted Haptique RS90 server.

In practical terms: users can set up and operate locally, without needing internet access or our hosted server for that configuration/control flow.

3. Haptique Music

Haptique Music is also part of this beta.

This is our local music and media layer inside Haptique, including local library support, playback control, player discovery, outputs, queues, radio, and the foundation for deeper local music server features.

What we want feedback on

Please test it in real setups and share:

1. What system you installed it on
2. Whether your config app connected successfully
3. Whether your Haptique RS90 connected successfully
4. What devices, integrations, or music outputs you tested
5. What worked well
6. What failed, broke, or felt confusing
7. What you want us to prioritize next

This is a beta, so expect rough edges. The goal now is to test the full local Haptique path in real environments: Haptique OS, local Fleet Server, Haptique RS90/config apps, and Haptique Music working together.

Thanks for being part of this. This is a big step toward Haptique running fully local, with the cloud no longer required for the core experience.

Your licenses will be released to your email address this week as we build the user database so for now you can connect your Haptique with local fleet server running on any machine and connecting Haptique and Config app pointed at the IP address of the machine running HOS. Look forward for an email to get your license copy for the Haptique OS. We also have discord community now for realtime discussion.

[Roland]

I’m logged in but somehow it doesn’t work here where can I find the extender token?
I can’t log in to the Hos app anymore Although I use the same password as in the browser.
The remote control cannot be connected via the browser either.
I find it all very complicated.

[ccsfounder]

You have to reset your extender and reconnect with the local server, there is no connection between cloud and local server so you have create new user in Admin side. You can do this via config app but first do the change server and provide IP of HOS to config app.

You should be at login screen on config app
Login using the new created user credentials and setup everything.
RS90 also need to be reset and there you will find change server option below the QR code. The whole process is documented here - RS90 Remote Overview | Haptique® OS

[Roland]

Here is some information about my attempt to connect to OS :

So I seem to be online.

Add a controller ? Where do I get the controller URL?!

Log in not working.

Which two IP addresses do I enter in this screen?!

I have the extender reset but it is still not recognized in the network it still has the same IP address and the same token.
A QR code is also briefly displayed or a window for it, but after a short time about 1 second directly disappeared again and on the screen it says I should use Chrome. I use Chrome.

[ccsfounder]

Can you confirm you are running Haptique OS on any local server or computer?

You need to first connect Config app to the running Haptique OS (local server IP)
Also the remote require the IP address of the server.

So first download server from and setup.

You cannot use the web configurator as it doesn’t connect to the local server yet - Also the webconfigurator link you are using was for testing - Live is here- config.haptique.tech