frogCloud adds convenience, not dependency
The building keeps working locally. frogCloud layers remote access, project sync and frogSIP push calls on top — optional, never mandatory.
- Optional
- never a dependency
- Local-first
- the building runs on-premise
- Push
- frogSIP smartphone calls
- Sync
- remote access & project sync
Why frogblue
A convenience layer on top of local-first control
The building keeps working locally
Automation, intercom and access run on-premise. If frogCloud is unreachable, the building carries on without it.
Remote access & project sync
Reach your installation from anywhere and keep projects in sync across devices — when you choose to enable it.
frogSIP push calls
frogCloud SIP delivers door calls to the frogSIP smartphone app with push notifications, wherever you are.
What frogCloud adds
Push calls, remote access and project sync
frogCloud adds remote connectivity, push workflows and cloud-assisted calling while preserving local-first control. A free account tier exists, and you can run the building entirely on-premise without it.
- frogSIP smartphone call push via frogCloud SIP
- Remote access to your installation
- Cloud project sync across devices
Security & data location
frogCloud is optional by design. Because automation, access verification and intercom logic run locally on the mesh, there is no master server that must be online for the building to function — and no single cloud system to compromise.
When you enable frogCloud, it adds remote access, project synchronisation and frogSIP push calling. Credentials and access rights remain encrypted and carried locally on the card; the cloud is a convenience layer, not the system of record.
Add the cloud when you want it
Talk to the team about remote access, push calling and project sync — entirely optional on a local-first frogblue building.