Recommended Minimum Hardware Specs (office / back-office workstation)
Processor (CPU): Quad-core, 2.5 GHz or faster (Intel 12th Gen Core i5 / AMD Ryzen 5 5000-series / Apple M1 or newer). Recent single-core speed matters more than core count, so a newer 4-core chip beats an older 8-core one.
Memory (RAM): 32+ GB recommended, 16 GB minimum. BuildOps is never the only thing running, and 32 GB allows heavy multitasking with Outlook, Teams, Excel and dozens of browser tabs open alongside live dispatch boards and job screens all day.
Storage: 256 GB or larger NVMe Solid State Drive, with at least 10 GB kept free for browser cache. Free space matters more than total capacity.
Graphics (GPU): Integrated graphics are fully sufficient (Intel Iris Xe, AMD Radeon, Apple M-series). Two things are required: browser hardware acceleration must stay enabled, and the GPU must support WebGL 2, since BuildOps renders 3D BIM/CAD models and large PDF drawing sets in the browser.
Display: 1920 x 1080 (Full HD) or larger, 1440 x 900 absolute minimum. Needed to view dense work orders, dispatch boards, purchase orders and asset trees without excessive scrolling. Note that browser zoom above 100% reduces usable screen space.
Internet Connection: Stable business broadband, 25 Mbps download / 5 Mbps upload or better, with latency under 100 ms. Consistency matters more than headline speed, since BuildOps runs entirely in the browser.
Do not trade CPU for RAM. If the budget forces a choice, a current-generation processor with 16 GB will feel better than a five-year-old processor with 32 GB. How responsive buttons and grids feel is governed by CPU, not memory.
Browser
Browser | Status |
Google Chrome (latest two versions) | RECOMMENDED |
Microsoft Edge (latest two versions) | RECOMMENDED |
Mozilla Firefox (latest two versions) | SUPPORTED |
Apple Safari 16+ (macOS) | SUPPORTED |
Internet Explorer, legacy Edge, anything released before 2021 | NOT SUPPORTED |
Keep browsers on auto-update. Pinning a browser version for years is the most common cause of BuildOps breaking for one department only.
Required browser settings:
JavaScript enabled
Local storage enabled and not auto-cleared on close (sign-in sessions and the data cache live there)
Pop-ups allowed for
buildops.com(reports, PDFs and invoices open in new windows)Cookies allowed for
buildops.com. Third-party cookies are not requiredHardware acceleration on
Ad-blockers and privacy extensions set to exclude
buildops.com
Operating System
Operating system | Status |
Windows 11 | RECOMMENDED |
macOS 14 Sonoma or newer | RECOMMENDED |
Windows 10 22H2 | WORKS, PLAN TO MIGRATE |
ChromeOS (current) | LIGHT BACK-OFFICE USE ONLY |
Windows 7, Windows 8.1, macOS 12 or older | NOT SUPPORTED |
There is no BuildOps desktop installer, so the operating system only needs to run a current browser. Microsoft ended mainstream support for Windows 10 in October 2025, so customers still on it should plan the Windows 11 migration. ChromeOS is not suitable for BIM or drawing review.
Network and Security (for customer IT administrators)
This is the section that causes most rollout problems. Ask customer IT to review it before go-live.
Allowlist these domains on port 443 in the firewall, web proxy, SSL inspection bypass list and any DNS filtering:
Domain | Purpose |
| Web app, APIs, sign-in, real-time updates |
| Authorization services |
| Photo, video and document storage |
| Search |
| Feature configuration |
| In-app support chat |
| In-app product guides |
| Maps and fonts |
| File upload and download |
| Error and performance reporting |
WebSocket connections must be permitted. BuildOps holds a persistent connection to wss://graphql.live.buildops.com/graphql for live dispatch and notification updates. Proxies that block or silently drop WebSocket upgrades are the most common cause of the app appearing stale or reconnecting in a loop. Check this first on any "data is not updating" report.
Also required:
TLS 1.2 or 1.3. Clients or middleboxes limited to TLS 1.0/1.1 must be upgraded. This includes any proxy, firewall or VPN concentrator terminating TLS on the customer side.
SSL inspection bypass for
*.buildops.comand*.buildops.org. Re-signing our certificates commonly breaks live updates and file uploads.No VPN required. Where a VPN is mandatory, use split tunnelling so BuildOps traffic goes direct. Back-hauling file uploads through a central concentrator is a frequent cause of one branch being slow.
Bandwidth planning: budget roughly 7 MB per full app load per user, plus photo and document uploads from the field.
Field Technician Mobile App
iOS: iOS 16.0 or newer (iOS 16.2+ for Lock Screen features). iPhone 11 or newer recommended. iPad supported.
Android: Android 9 (Pie) or newer, Android 12+ recommended. 4 GB RAM or more.
Both platforms:
64 GB device storage minimum, 128 GB recommended for photo-heavy work
8 GB free space minimum, 16 GB or more recommended, since the app downloads an offline copy of the company's data
Wi-Fi for the first sync. The initial download is large and will fail on a nearly-full device
Cellular data plan with a real allowance for ongoing photo and signature upload
Location and camera permissions granted for time tracking, geo-stamping and job photos
Not supported
Internet Explorer, legacy (EdgeHTML) Edge, or any browser released before 2021
Windows 7, Windows 8.1, macOS 12 or older, iOS 15 or older, Android 8 or older
Environments that block JavaScript, local storage, or WebSocket connections
Shared or kiosk browsers that wipe site data on every close. These work, but users re-authenticate every session and lose all caching benefit
Virtual desktop environments (Citrix, VDI, RDS) with under 2 vCPU or 4 GB RAM per session, or with GPU acceleration disabled. VDI is workable but each BuildOps session must be sized like a real desktop, not a terminal