Bearing

Security & Reliability

Your project data is critical infrastructure. It is encrypted in transit and at rest, held locally on the device so the job keeps moving without a signal, and synced on Google Cloud.

Encrypted in Transit and at Rest

All scheduling data, blueprints, and communication are encrypted at rest using AES-256 and in transit via TLS 1.3. We maintain strict role-based access controls so only authorized people in your workspace can view your sensitive project details.

Local-First Offline Reliability

Traditional cloud software fails when you lose cell service on a remote job site. Bearing's local-first CRDT architecture keeps the schedule, daily reports and field capture working with no signal, and merges concurrent changes without data loss when you reconnect. AI assistance, photo classification, voice transcription and billing need a connection — the app is offline-capable, not offline-only.

The Calculation Runs on Your Device

The CPM engine is not a server round-trip. The whole dependency network is recalculated locally, so the critical path updates as fast as you can type — on a laptop in the trailer or a phone with two bars.

Auditing

Change orders and obligations each keep a record of who made the change, what changed, and when. Subcontract payments keep a full history of every draw — date, amount, and reference, not a log of who changed what. Schedule activities and dependencies do not currently keep any change history. SOC 2 Type II certification is on the roadmap and is not in place today.

Bearing Assistant1