The same architecture on your hardware or ours.
A cluster of your own in North America, or your own machines on Enterprise.
Standard plans run on a cluster dedicated to you: its own virtual server in North America, shared with no other customer. On an Enterprise license the same Docker images run on your hardware or your cloud account: AWS, Azure, GCP, bare metal or a private LAN.
On your own infrastructure, customer and event data never leaves your network. The server's only scheduled outbound call is a daily license check that sends a license ID and a hashed install fingerprint. The desktop app also checks for updates, which you can turn off.
Reduce dependence on third-party analytics vendors, subprocessors, and external data paths.
Marver sends your data to no outside analytics service. All data processing, identity resolution, and query execution happens inside the Marver cluster, wherever it runs. The one outside call a self-hosted server makes is the daily license check.
On your own infrastructure there are no subprocessors in the data path at all. On a hosted cluster there is one, the company that provides the virtual server, and we name it before you send any data. Your security team reviews one vendor, not a chain of agreements.
Run regulated workloads with TLS, role-based access control, and audit logs of configuration and governance changes.
The storage and query APIs check every request. Each one carries a bearer token: an access key issued to one person in the Access Control console, or the setup token used for first installation. An admin can revoke a key at any time.
Three roles: read-only (query + reads), operator (+ mutations: backfill, config/schema writes), admin (+ access keys, governance and retention controls). Only the SHA-256 of each key is stored.
On a hosted cluster, TLS is enforced on every connection from the Workbench to the cluster. On your own infrastructure, the TLS deployment profile encrypts traffic between every component, and the data path between collection, storage and query adds mutual TLS, where each side authenticates the other.
Enterprise licenses can run fully offline on your own hardware: no license server, no outbound server calls.
Air-gapped Enterprise deployments use a signed offline license, so the server makes no outbound calls at all, not even a daily license check. Turn off the desktop app's update check and nothing leaves the network. If your network can't reach the internet, Marver still works. A self-hosted install that is not air-gapped checks its license once a day. After 30 days of failed checks it stops taking new events, while queries and exports keep working. Air-gapped installs have no such limit.
Retention and deletion follow your policy, on storage you own or on a cluster dedicated to you.
The raw event archive is plain NDJSON text. On your own infrastructure the disks are yours. On a hosted cluster we back up nightly and apply the retention and deletion schedule you set.
If you stop using Marver, the raw event archive remains readable as plain text without it. The query store is Parquet in a Marver container, rebuilt from that archive.
Short answers to common security questions.
| Question | Answer |
|---|---|
| Who is the vendor? | Chip Hosting Solutions LLC, a US company registered in SAM.gov (UEI C9BWJGM58TP5, CAGE 228Q2). Marver is not affiliated with or endorsed by Adobe. |
| Where does customer data live? | On a hosted plan, a virtual server in North America used by you alone. On Enterprise, your own infrastructure. |
| Who can access a hosted cluster? | Chip Hosting Solutions holds server admin access to operate it. Your team holds application admin access: users, keys, schema and data. |
| Are hosted clusters backed up? | Yes, nightly. |
| Does any data leave the network? | On your infrastructure: a license ID + hashed install fingerprint, once per day, plus the desktop app's optional update check. Enterprise air-gap: nothing. |
| How is access controlled? | Bearer token authentication with per-principal keys and three roles (read-only, operator, admin). |
| Are passwords/secrets stored in plaintext? | No. Only SHA-256 hashes of access keys are stored. |
| Is traffic encrypted? | Hosted: TLS is enforced on every Workbench connection. Self-hosted: the TLS profile covers all component traffic, with mutual TLS on the data path between collection, storage and query. |
| Is there SSO or MFA? | Not today. Access is by per-person keys that an admin can revoke at any time. |
| Can it run air-gapped? | Yes. The Enterprise tier supports fully offline deployment with a signed offline license and no outbound server calls. |
| What happens if you go out of business? | The raw event archive remains readable as plain NDJSON. A self-hosted install that cannot reach the license server stops taking new events after 30 days unless it holds an offline license; queries and exports keep working. |
| Is there a SOC 2 / ISO 27001 certificate? | No. We are a small company and have not been audited. We provide an architecture document and written answers to your security questionnaire. If your policy requires a SOC 2 report from any vendor that holds data, Marver on your own infrastructure under an Enterprise license is the fit. |
Every question gets a written answer from the engineer who built it. No sales team.