System requirements & readiness
- · Use this checklist before blaming betas—you need disk space, steady internet to download and sign into services, plus patience for Gmail-sized mailboxes.
- · Exact numbers drift with TinyHumans releases; spot-check their README whenever you upgrade.
- · Corporate laptops: IT may block installers or SSO—coordinate with admins using the Operational notes column.
Skim vertically: if nothing looks impossible on your laptop, proceed to Install guide. Save deep compliance questions for your IT team plus TinyHumans’ own docs—we summarize common blockers below.
| Area | Recommended guidance | Operational notes |
|---|---|---|
| Supported OS | Official builds target desktop macOS, Windows, Linux. | Prefer GUI installers linked from TinyHumans; scripts exist for scripted installs. |
| CPU architecture | Match published artifacts (Intel vs Apple Silicon vs Linux x86_64/ARM builds). | If install.sh targets "Linux x64" per README, verify binary matches ARM hosts before blaming OAuth. |
| Memory floor | 4 GB RAM minimum cited in onboarding docs. | 16 GB+ realistic for heavy Gmail volumes, sprawling repos, or local models concurrently. |
| Storage | Fast SSD strongly recommended. | Vault + SQLite + connector caches spike as mail threads or logs ingest. |
| Display & input | 1080p+ comfortable for dual-pane UI tooling. | Voice + Meet agents rely on microphones/cameras; OS toggles revert if revoked mid-flight. |
| Network | Reliable WAN for installers, OAuth, hosted models. | Purely offline usage is unrealistic unless adopting fully local stacks per docs. |
| Accounts | Product login + discrete OAuth approvals per SaaS connector. | Plan IT reviews for SSO / MDM fleets; revocation happens at vendor dashboards. |
| Dev tooling | End users seldom need Xcode/Rust toolchain unless compiling from Git. | Contributor prerequisites live in README + CONTRIBUTING.md at https://github.com/tinyhumansai/openhuman. |
When to pause the install
- You cannot grant Accessibility / Input Monitoring on macOS due to MDM locks.
- Corporate SmartScreen removes unsigned binaries—you need packaged proof from IT.
- You expect zero cloud egress—the hosted model tiers likely violate internal policy.
Ready? Jump to the Start-here flow once your machine matches—or open OS-only footnotes if you ran into SmartScreen/Gatekeeper quirks specifically.