Manta is MIT licensed and self-hosted. No account, no telemetry, no vendor, no hosted control plane. You can read every line of the server, the desktop client and the install script before you pipe it into bash. We would rather you did.
Open source in this product is not a marketing line. The repo carries a working MIT licence, the install script is in the repository, and every line of the server, the desktop app and the phone client is on GitHub.
The product runs on hardware you own. There is no hosted control plane to sign up for, no usage telemetry leaving the box, and no seat count to grow into a bill.
The single sharpest difference between an open source product and a "self-hosted" one is whether the install can be read before it runs. Manta's can.
Five questions, answered in full.
On GitHub at github.com/antoinedc/MantaUI. The server, the Electron desktop app, the React renderer, the phone client and the install script all live in the same repository.
MIT. The full text is in the LICENSE file at the root of the repository. It is permissive: fork it, modify it, ship a derivative, keep the copyright notice.
Everything. Transcripts, uploads, secrets, configuration, schedules, peer metadata, ingress choice. The only outbound traffic is your agent talking to its model provider, and a small push payload carrying the session name when you turn on phone notifications.
Yes. Fork the repo, point the push routing at your own gateway, edit the manifest. The push and webhook modules are designed to be replaced. The same goes for the install script, the installer, and the desktop app.
Only to your model provider and to APNs, when you have phone notifications turned on. There is no analytics SDK, no telemetry beacon, no usage ping. The pricing page covers what you actually pay for.
Free, open source, MIT. Runs on a Linux VPS or a Mac you already own.
$ curl -fsSL https://mantaui.com/install.sh | bash