VaultSync / GeoNum Engine
Licensed CLI · Windows x64 & Linux x86_64 · build 1.0.1

GeoNum Engine.
Every result ships with its own trust verdict.

The licensed, proprietary command-line precision engine of the GDBS platform. Drift-tracked arithmetic with a trust response on every result - so you know whether to rely on a number, not just what it is. A single compiled binary. Runs locally. No cluster, no service for computation. Source is not shipped.

trust verdicts PRECISE / DRIFTING / UNRELIABLE / ERROR
distribution single native binary
patent U.S. 63/970,430 pending
Define

Precision you can audit.

Not a faster float. A number system that carries its own uncertainty forward and tells you when to stop trusting a result.

Drift-tracked precision

Every computed value carries a drift figure and a relative-uncertainty figure. Precision is tracked through the calculation rather than assumed. GeoNum precision is drift-tracked, not a fixed digit count.

Trust response

Each result is labelled PRECISE, DRIFTING, UNRELIABLE, or ERROR, derived from the engine's own drift - so you know whether to trust a number, not just what it is.

Deterministic and local

The same inputs produce the same outputs. A single small native binary; the compute path needs no network and no cluster. The compiled binary is the licensed artifact.

Commands

Two commands. Honest output.

Self-documenting CLI: geonum help · geonum docs · geonum support "..." (emails the maintainer directly).

geonum compute

Evaluate a math expression or a named formula. Variable bindings, JSON in/out, and batched JSON input. Returns the value plus the trust verdict.

# single expression with built-in constants
geonum compute --expression "hbar*c^3/(8*pi*G*1.989e30*kb)"

# label = rhs and bound variables from a file
geonum compute --expression "E = D*C^2" --params domain.json

# batched JSON in, JSON out (array of jobs in -> array of
# results out; per-item zone/precision/label override)
geonum compute --input batch.json --output results.json
geonum validate

Run a computation against a built-in MPFR-256 reference and get PASS/FAIL plus the trust verdict and the engine's drift.

geonum validate --domain hawking --precision 60

# JSON report for CI / audit pipelines
geonum validate --domain hawking --output report.json

geonum version

Honest by design: an unknown identifier or unsupported function returns a clear unsupported status with trust ERROR - never a fabricated number. --precision is recorded as the requested precision; GeoNum precision is drift-tracked, not a claimed digit count.

Usage

Call GeoNum from your stack.

There is no SDK to install and no service to call. You shell out to the licensed binary and parse the JSON it prints to stdout - the same JSON shape geonum compute emits on the command line. Exit code 2 means licensing; the trust verdict rides along on every result.

Run the binary with subprocess, parse stdout with the standard json module.

# Call the licensed binary, parse the JSON it prints to stdout.
import json, subprocess

def geonum_compute(expression, params=None):
    cmd = ["geonum", "compute", "--expression", expression]
    if params:
        cmd += ["--params", json.dumps(params)]
    proc = subprocess.run(cmd, capture_output=True, text=True)
    if proc.returncode == 2:            # exit 2 = licensing
        raise RuntimeError("GeoNum licensing: " + proc.stderr.strip())
    return json.loads(proc.stdout)

r = geonum_compute("E = D*C^2", {"D": 1.989e30, "C": 2.99792458e8})
print(r["value"], r["trust"])   # value + PRECISE / DRIFTING / UNRELIABLE / ERROR

Same contract in every language: an unknown identifier or unsupported function comes back as status: "unsupported" with trust ERROR - never a fabricated number. For high throughput, write a JSON array of jobs and call geonum compute --input batch.json --output results.json once instead of spawning the binary per calculation. The binary must be on PATH (or pass its full path); set GEONUM_LICENSE_KEY in the process environment.

Download

Get the binary. Trial starts on first run.

The download is the full engine - not a feature-gated demo. On first run it self-enforces a 3-day evaluation. Subscribe to a tier for a license key and the same binary keeps running.

Each zip: binary + LICENSE + reference + SHA256SUMS. Linux build is musl-static - runs on any modern x86_64 distro (Ubuntu, Debian, RHEL, Alpine).
Once installed: geonum help, geonum docs, geonum support "...".
Licensing

Flat pricing. No contracts.

Every tier is the same binary with no feature gating. 3-day free trial. No discounts. No annual contracts. Cancel anytime.

Individual
$60/ month

For a single practitioner.

  • Full CLI, no feature gating
  • compute + validate + trust response
  • Single user
Infrastructure
$240/ month

Embed in internal pipelines at a flat cost.

  • Unlimited infrastructure use
  • Embed in internal pipelines
  • Flat predictable cost
  • Air-gap / long-offline token on request

OEM / sub-licensing (embedding GeoNum Engine in another product) is a separate written agreement: licensing@getvaultsync.com.

GeoNum Open vs GeoNum Engine

GeoNum OpenGeoNum Engine
WhatThe published v1 number system - in-browser calculatorThe full proprietary engine as a licensed CLI
PriceFree, citable$60 / $120 / $240 per month
DistributionRuns in your browserSingle native binary you run locally
CitationDOI: 10.5281/zenodo.18753425Proprietary · patent pending U.S. 63/970,430
Use itOpen the calculator →Download the CLI →
Security & Trust

Your computational data never leaves your device.

That's not a policy - it's the architecture. GeoNum Engine runs entirely in a native binary on your machine. Inputs, parameter files, batched JSON, computed results, drift figures, trust verdicts, validation reports - none of it is transmitted to or stored on VaultSync servers. There is no server-side repository of your computation, so there is nothing to breach, subpoena, or leak. The only network traffic the binary ever emits is a periodic license check that carries your license key (which is the entitlement, not your data), with a 14-day offline grace so the engine keeps working even when our license server doesn't.

What stays on your machine

Everything you compute. Source is not shipped - the compiled binary is the licensed artifact. The compute path sends none of your data over the network. The binary's only outbound call is a periodic license check that carries your license key and nothing about your computation. All --input, --params, and --output files are read from and written to your local disk. Trial state and an optional license-key file live in ~/.geonum/ under your user account, protected by your OS's normal home-directory permissions. VaultSync cannot access, recover, or produce your computational data, because we do not possess it.

What we hold, and how we protect it

License administration only: the buyer email Stripe collects at checkout, the license-key entitlement record (tier, last verify timestamp), and standard payment metadata held by Stripe. That data is encrypted in transit (TLS 1.2+) and at rest, hosted in the United States, with role-based access controls. Payment processing is handled entirely by Stripe under PCI-DSS compliance (SAQ-A); we never receive or store card or bank details.

AreaImplementation
Local compute pathAll math runs in the native binary on your machine. The compute path sends none of your data over the network - no telemetry, no analytics, no crash reporting, no anonymous pings. The binary's only outbound call is the periodic license check described in the next row.
License verificationOne HTTPS GET to license.getvaultsync.com/v1/check per compute/validate invocation. Carries product name, binary version, and your license key. Sends nothing about your computation. Built on rustls - no native OpenSSL dependency.
Offline grace14-day window from the last successful verification. If our license server is unreachable inside the window the binary keeps working and tells you days remaining. Outside the window it denies cleanly with exit code 2 rather than silently failing. Air-gapped or long-offline sites: Infrastructure-tier customers can request a longer or perpetual offline-licensed token under a separate written agreement (licensing@getvaultsync.com).
License key storageRead from the GEONUM_LICENSE_KEY environment variable (preferred) or ~/.geonum/license. Never logged to stdout/stderr. The key value never appears in geonum support diagnostics.
Trial enforcement3-day evaluation tracked locally in ~/.geonum/state (two integers: first_run, last_ok). No phone-home for trial start. No card needed to evaluate.
Data in transitTLS 1.2+ to license.getvaultsync.com. No other outbound traffic. The geonum support command opens your local mail client to email the maintainer directly - the message does not pass through VaultSync.
Data at rest (license records only)AES-256 encryption on stored license records; access restricted via role-based controls; US hosting; PCI-DSS via Stripe for payment.
Process isolationSingle process, no IPC, no temp files outside ~/.geonum/. The binary itself is statically linked on Linux (musl) and self-contained on Windows - no shared-library hijack surface.
Honest output disciplineAn unknown identifier or unsupported function returns an explicit unsupported status with trust ERROR. An unknown domain returns unknown_domain. validate with no built-in reference returns no_reference and exits 1. The engine never fabricates a number, and never fabricates a reference.
Honest exit codes0 success · 1 usage error / no built-in reference / batch run with any non-ok item · 2 licensing (trial expired, key rejected, or could not verify within offline grace) · 3 validate ran but the result FAILED its tolerance.
Supply chainEach release zip ships a SHA256SUMS file alongside the binary. Reproducible builds via cargo build --release (Windows) and cargo zigbuild --target x86_64-unknown-linux-musl --release (Linux). Source is not shipped; the compiled binary is the licensed artifact.
Hosting (license server only)US-based; TLS at the edge; license records segregated from any other VaultSync product database.
Payment dataStripe Checkout redirect; cardholder data never touches VaultSync (SAQ-A, PCI-DSS).

What we don't do

We do not transmit your computational inputs, parameters, or results to VaultSync - ever. No telemetry from the binary. No anonymous usage pings. No crash reporting back to us. We do not sell, share, rent, or trade user data. We do not use your data, inputs, or results to train any AI, machine-learning, or language model.

Server-side, disclosed plainly

The only server-side feature is the license check: an HTTPS GET to license.getvaultsync.com that carries the product, binary version, and your license key. The response is used only to gate the current invocation and update the local last_ok timestamp. We never receive your math, your parameters, or your results.

On formal attestations

VaultSync does not currently hold a SOC 2 or equivalent third-party attestation. Because GeoNum computation is local, the data surface a SOC 2 audit typically examines - customer data held on the vendor's systems - does not exist here. For organizations whose procurement requires a formal attestation, contact legal@getvaultsync.com.

Service & support

Direct: support@getvaultsync.com, or run geonum support "..." from the CLI to open a pre-addressed diagnostic email. Support hours: Monday-Friday, 9:00 AM-5:00 PM Central Time, excluding US federal holidays, with initial response within one business day. Because the engine runs locally, GeoNum keeps working on your machine even during a license-server interruption (subject to the 14-day offline grace).

TierSupport commitment
Infrastructure ($240)Contractual SLA per the EULA. Initial substantive response within 1 business day; dedicated success contact; custom SLA available on request.
Commercial ($120)Contractual SLA per the EULA. Initial substantive response within 1 business day; priority handling.
Individual ($60)Best-effort priority handling, same 1-business-day response target on a commercially reasonable basis.
3-day trialStandard best-effort handling.

Documentation: the proprietary EULA ships inside every release zip as LICENSE. Procurement and security questions: support@getvaultsync.com or run geonum support "..." from the CLI. Patent pending - U.S. Provisional 63/970,430.

How licensing works

Trial → subscribe → run.

1 Trial

Download and run the CLI. The binary self-enforces a 3-day evaluation from first use - no card needed to evaluate.

2 Subscribe

Pick a tier and check out. You receive a license key by email. Set GEONUM_LICENSE_KEY and the CLI verifies it remotely, re-confirming periodically.

3 Manage

Billing is monthly. Cancel anytime from the billing portal - no lock-in, no termination terms to negotiate.

4 Compliance

Source is not shipped. The compiled binary is the licensed artifact, protected by the GeoNum Software License Agreement. Patent pending.