officehours.space

What It Is

Office Hours is not a traditional email, SMS, or voice service. Instead, it is an “ambient online status” app for physical spaces. It aims to bring the idea of Slack’s green online dot into real-world locations: when members enter the geofence of an office, studio, coworking space, or shared house, friends who share the same Hub can see that they are currently present—without manual check-ins or mass messages.

Core Capabilities and Architecture

Its core channel is closer to real-time presence inside a mobile app than to email, SMS, or voice. The system consists of three parts: an iOS app, an identity service, and a self-hosted Hub Server. The mobile app handles background geofencing detection and real-time status display; the Hub Server uses Node.js, SQLite, and WebSocket to push current status; the identity service handles phone number authentication, key issuance, and friend relationships, but does not store presence data. The server side supports Docker deployment and can run on Railway, Render, Raspberry Pi, or other Docker environments. It also claims that the source code is available on GitHub.

Privacy and Compliance

A key strength of Office Hours is its clear privacy boundary: the app does not read or store GPS coordinates; it only knows whether a user is inside the geofence of a given Hub. It stores only the current present/not present state, and does not retain timestamps, access logs, or location history. Users can control sharing per Hub or pause it globally. The description also states that there are no third-party analytics, crash reporting, or advertising SDKs. The Hub Server stores only anonymous user IDs and public keys, and uses Ed25519 signatures to verify identity locally. However, the text does not mention formal compliance certifications such as GDPR, SOC 2, or ISO 27001.

Pricing and Performance

The page does not disclose any rates, subscription plans, commercial licensing, or payment methods. On performance, it only states that arrivals and departures are detected automatically via background geofencing and that updates are pushed in real time via WebSocket. It does not provide information on delivery rates, latency, concurrency capacity, SLA, or disaster recovery. As a result, it still appears early-stage from the perspective of enterprise-grade communications infrastructure.

Pros, Cons, and Best-Fit Users

Its advantages are that it is low-distraction, automated, privacy-friendly, and allows communities to control their own Hub data. The drawbacks are that it is still in TestFlight Beta, the text only mentions iOS with no visible Android/Web support, and it lacks commercial support or stability commitments. It is best suited for small communities, creator studios, hackerspaces, coworking teams, and similar groups that want to know “who is on site” without using continuous location tracking or check-in systems.

China Access

The text does not provide information on accessibility in mainland China, app distribution, phone number authentication coverage, or payment options, so its China access status can only be rated as unknown. For deployment in China, potential concerns include TestFlight availability, network connectivity for self-hosted servers, SMS/phone authentication service coverage, and alternatives such as WeCom, Feishu, WeChat group check-ins, or access control systems.