The cluster is where your physics goes to scale.
The browser is where your physics goes to get verified.
Computational research spends the validation phase the same way it spends the production phase: standing up a cluster, waiting in the job queue, and paying for compute by the hour, all before you know your setup is right. GDBS moves that early work - method development, parameter sweeps, validation, and teaching - onto the device you already own, and keeps production where it belongs, on HPC. It is not another infrastructure line item; it is the cheap local check that keeps the cluster hours you do pay for going to production runs that finish, not exploratory jobs that crash on numerical drift.
Provisioning, queue wait, and install collapse to opening a browser tab. The iteration that decides whether your setup is even correct happens in seconds, not after an allocation request clears.
The browser-scale prototyping phase runs at zero marginal compute cost on hardware you already have, so paid cluster hours go to production runs, not to debugging a setup.
Every value carries its drift and a trust verdict, so you stop re-running jobs just to convince yourself the number is real. Uncertainty is reported, not assumed.
Illustrative, not a guarantee. A team that runs a few hundred exploratory simulations to settle a method, each a couple of cluster-hours plus a queue wait, can move that exploration in-browser and spend cluster time only on the handful of production runs that follow. The saving is the avoided exploratory cluster hours plus the engineer-hours lost to the queue; the exact figure depends entirely on your workload and rates. Production-scale runs still belong on HPC.
Three browser platform shifts matured at once, and GDBS adds the precision layer that makes them trustworthy for science and engineering.
Near-native compute in the browser. The numerical engines compile to WebAssembly and run fast enough to be real solvers, not toy demos, on an ordinary laptop.
Direct GPU compute in the browser, not a graphics workaround. The same class of parallel hardware that drives a cluster node is reachable from a tab, so GR-MHD and spectral solvers run on your own GPU.
Access to tensor and NPU hardware the GPU path cannot reach, pairing neural-accelerator silicon with the precision engine for the largest in-browser problems.
The proprietary piece. Browser numerics are only useful if you can trust them; GeoNum carries the error of every operation forward, so a result in a tab is as auditable as one from the cluster. Patent pending.
Standard databases store data and return it. GDBS stores data geometrically - every value knows where it lives in precision space, how much it drifted to get there, and what its uncertainty is. That's not a feature. That's a different physics.
2048-shade zone/shade architecture. Drift compartments track error at every multiplication step - transparently, not silently.
One GeoNum class, domain-specific zone configurations. Theory, Quantum, Fluids, Plasma, Materials, Geophysics, Ballistics.
8-byte content addressing. 5D geometric positioning in semantic space. Automatic relationship discovery between data nodes.
getUncertainty() and getRelativeUncertainty() on every result. No black box. Every computation auditable, every drift visible.
A unified geometric computing stack: precision, search, and reasoning. Precision (GeoNum) - Search (SyncSearch) - Reasoning (CORA), all on GDBS.
The intelligence node. A browser-native AI assistant with persistent geometric memory - knowledge is stored in GDBS, not in a context window. Responses are grounded, traceable, and domain-aware.
Enterprise search without the cluster. GDBS geometric positioning replaces the inverted index - semantic proximity in 5D space means relevance is a geometry problem, not a keyword problem.
The precision core of GDBS as a licensed CLI. Every result carries a drift figure and a trust verdict derived from the engine's own propagation - so you know whether to rely on a number, not just what it is.
Each result below is computed by the engine and compared against a published scientific reference: a detection paper, a textbook value, or a convergence theorem. Platform values are reported as measured; references are cited as published. Nothing here is a curve fit.
Run Live BenchmarksReproduces LIGO's published GW150914 final black-hole mass to 0.13% (spin to 0.65%, chirp mass to 0.4%), checked against Abbott et al. (LIGO/Virgo). Computed and compared, not fitted to the detection.
The spacetime (BSSN) evolver is fourth-order accurate. The order falls out of grid refinement - measured 3.946 against the theoretical 4 on the standard Apples-with-Apples testbed, not asserted.
T_H reproduced across 60 orders of magnitude (10⁻³⁴ to 10⁻¹⁴) to 0.27% of the analytical closed form, GeoNum drift 0.345 shades. IEEE 754 degrades silently at this scale; GDBS tracks every digit.
Validated physics with transparent uncertainty, at a fraction of cluster cost. Enterprise tops out at $75k/yr - full platform, HPC Lab, dedicated SLA. No job queue. Transparent uncertainty on every output.
Every result is reproducible in your browser. No cluster access required.
Reproducible against the engine's own release-gating test suites - gravitational-wave detection, numerical-relativity convergence, density-functional chemistry, fluid boundary layers, and precision chains - at gdbs.getvaultsync.com.
From exploratory tools to full research workflows. No credit card required to start.
3-day full trial on signup. No credit card.
.edu required. Per 5 users. Student $99 · Faculty $249 · Lab $3,500.
Commercial physics modules, multi-physics coupling, SLA. HPC Lab + all addons on Enterprise. BSSN, LIGO, GRMHD sold as separate addons. ($25k-$75k/yr annual)
We're accepting a limited cohort of research institutions and engineering teams for full research access. Participants get the complete platform - Multi-Species MD, coupled MD↔FEM, batch sweeps, and HPC Lab - at no cost during the program.
Academic and student pricing available - contact us directly. We respond to everything.
The Theory Lab runs Hawking radiation, LIGO gravitational-wave reproduction, and seven physics domains live - right now, in your browser. No signup. No queue. No black box.
Prefer your calendar? Download a 30-minute hold (.ics) and we confirm the time by email.
That's not a policy - it's the architecture. GDBS runs its physics and precision computation entirely in your browser via WebAssembly. Your inputs, parameters, and computed results are processed locally and are never transmitted to or stored on VaultSync servers. There is no server-side repository of your research data, so there is nothing to breach, subpoena, or leak. This is a stronger guarantee than most vendors can make, because they hold your data and promise to guard it; we simply never receive it.
Computational inputs, parameters, and configurations. Computed results, charts, datasets, trust classifications, and downloadable bundles. All of it is generated client-side and saved to your local storage. VaultSync cannot access, recover, or produce your computational data, because we do not possess it.
API keys for third-party data sources (e.g. arXiv, Anthropic, your own services) are stored only in your browser's local storage and are never sent to VaultSync. They are read by the client at the moment of the outbound request and accompany only that request to its destination.
We store only account data - your name, email, institutional affiliation, subscription tier, and login timestamps - for license administration and authentication. That data is encrypted in transit (TLS/HTTPS) and at rest, hosted in the United States, and access is restricted to authorized personnel through role-based controls. Payment processing is handled entirely by Stripe under PCI-DSS compliance; we never receive or store card or bank details. The implementation details are below.
| Area | Implementation |
|---|---|
| Client-side compute | Engines run in-browser via WebAssembly. Per the GDBS Data Use Agreement (DUA), customer inputs and computed results are processed locally and not transmitted to or stored on GDBS servers. |
| Data at rest (account data) | AES-256-GCM (random 12-byte nonce + auth tag per write); every server-side collection encrypted; key derived from a dedicated DataProtection key with fail-loud decryption. |
| Data in transit | TLS 1.2+ terminated at the edge; HSTS; no cleartext fallback. |
| Password storage | BCrypt hashed (no plaintext, no reversible hash). Constant-time verify, including a dummy hash on unknown-user paths to prevent enumeration. |
| Session auth | JWT (HS256) with short-lived access token + refresh token; refresh enforces the disabled-account check; reset tokens are atomically consumed (single-use, race-free). |
| Authorization | Role-based access control on all admin and investor endpoints; API keys capped to non-admin scope (admin actions require an interactive session). |
| Path / injection | Strict charset validation on collection identifiers; resolved paths verified inside the data root; GQL identifiers and string literals safely escaped; arXiv id regex-validated. |
| CORS | Explicit allowlist (no AllowAnyOrigin); bearer tokens, no credentialed cookies. |
| Rate limiting | Per-IP throttling on authentication and anonymous endpoints to deter credential stuffing and automated abuse. |
| Request size limits | Bounded request bodies on compute and substrate endpoints; usage-log field lengths capped. |
| License keys | 128-bit entropy; constant-time comparison. |
| Payment data | Stripe Checkout redirect; cardholder data never touches GDBS (SAQ-A shape, PCI-DSS). |
| Audit logging | All API calls logged with session id, action, and timing; admin activity has a dedicated review surface. |
| Hosting | US-based; TLS at the edge. |
We do not sell, share, rent, or trade user data - ever, to anyone, for any purpose. No advertising. No data brokers. No third-party analytics beyond anonymized crash reporting. We do not use your data, inputs, or results to train any AI, machine-learning, or language model.
A few features - CORA retrieval, documented API endpoints, and the in-app support ticket - do send data to our servers to return a result. In those cases, data is used only to service the request and is not retained after the session ends, except active CORA session context during a live session. Everything else stays local.
VaultSync does not currently hold a SOC 2 or equivalent third-party attestation. Because GDBS computation is client-side, 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 us at legal@getvaultsync.com to discuss your specific requirements.
Support is available Monday-Friday, 9:00 AM-5:00 PM Central Time, excluding US federal holidays, via in-app ticket and email, with an initial response within one business day. Pro and Enterprise tiers include this as a contractual commitment. Because computation runs locally, GDBS keeps working on your device even during a server-side service interruption.
| Tier | Support commitment |
|---|---|
| Enterprise | Contractual SLA per the EULA. Initial substantive response within 1 business day; dedicated success contact; custom SLA available on request. |
| Pro | Contractual SLA per the EULA. Initial substantive response within 1 business day; priority handling. |
| Standard / Plus | Best-effort priority handling, same 1-business-day response target on a commercially reasonable basis. |
| Academic / Free | Standard best-effort handling. |
Documentation: EULA (PDF) · DUA (PDF) · Privacy. Additional documentation available under NDA - support@getvaultsync.com.
Licensing, investment, integration - we answer fast. VaultSync Solutions Inc., Arkansas, USA.
Other VaultSync products