Every MeshVault install runs on a dedicated, compatible machine that belongs to you, not a shared cloud account. Team size matters, but the final spec also depends on model choice, data volume, and how many agents need to run at once. We confirm it during your audit.
You end with a running system, your staff configured, and your hours back.
We come in, map your work, and quote a fixed price. The audit fee credits in full toward your install.
We install the machine, load your staff, and connect your business tools. Nothing to configure yourself.
We train you and your team on requests, approvals, and what each agent owns before we hand over the keys.
Ongoing maintenance, updates, support, and continued tuning keep the system secure and useful.
You will need a dedicated, compatible machine for the install. Team size matters, but the final spec also depends on model choice, data volume, and how many agents need to run at once. The audit sizes the spec, not a price tier.
The usual fit for a solo owner or small team. A compatible Mac you already own may qualify after the audit.
Built for growing or departmental teams, larger local models, and heavier multi-agent workloads. An equivalent system may also fit.
We confirm the hardware in your fixed install quote. You buy it directly, or we pass it through at invoice cost. You see the receipts either way.
Every install needs a compatible, customer-owned node. Most solo owners and small teams use a current Mac mini-class system. Growing teams or heavier local-model workloads may need DGX Spark-class hardware or an equivalent. We confirm the final spec during the audit. You buy the hardware directly, or we pass it through at invoice cost.
Yes, for teams up to about fifty people. We configure secure access for each person and shared agents for the departments that need them. The hardware spec scales with that headcount.
No. If you can text and tap Approve, you can run it. We handle the technical work and train you on the system we install.
You keep the hardware, files, and memory. MeshVault provides an offboarding handoff; components that depend on separate third-party services remain subject to those services.