Live - GDBS v1.0.0 · Windows x64

Do the validation work
before you pay for the cluster.

For researchers who need to develop, check, and de-risk a method before spending HPC budget, queue time, and an allocation grant. Run real validated engines in the browser - the Blasius boundary layer to 0.4696, GW150914 to 0.13%, a trust verdict on every result - with no install and no queue, then take the validated setup to HPC for the production run. GDBS is the honest front end to the cluster, not a replacement for it.

The database that
knows its own uncertainty.

GDBS is a geometric database system that runs real, validated physics and reports how much to trust every result. Every computation carries its error. Every result is verifiable. No black boxes. No hidden drift.

Not a supercomputer.
A bridge to one.

In plain terms: GDBS runs real, validated physics in your browser, and it reports how much to trust every result instead of asking you to assume. It is where you prototype, develop a method, validate it, and teach, with no queue and no allocation to request. The production-scale runs still belong on HPC. GDBS gets you ready for them and points the direction; it does not pretend to replace them.

A live compute API.
We expose the access, not the engine.

Authenticate and POST a physics function; the API routes it to your own connected browser node, where the real engine runs on your GPU and returns the result with its trust verdict when you poll. The engine and your data never touch our servers, so there is nothing on our side to breach or subpoena. The same engines the app uses, now scriptable.

General-relativistic magnetohydrodynamics,
evolved on your own GPU.

GDBS evolves a magnetized accretion torus on the GPU in your browser. A representative run held the magnetic-field divergence to 2.37e-4 under constrained transport, kept every conservation law in check, and reported a trust verdict on every observable instead of asking you to assume one. No cluster to schedule, no queue to wait in, no wall-time allocation to request.

LIGO's GW150914 black-hole merger,
reproduced to 0.13% in the browser.

The final black-hole mass lands within 0.13% of the published value and the final spin within 0.65%, checked against Abbott et al. (LIGO/Virgo). The result is computed and compared, not fitted to the detection, and it runs on the device in front of you.

The Hawking temperature, across 60 orders of magnitude,
held to 0.27%.

GDBS reproduces the analytic Hawking temperature from the quantum scale to the cosmological one and stays within 0.27%, where ordinary double precision quietly loses digits. The drift of every step is carried forward, so you can tell which results to trust.

A fourth-order spacetime solver,
convergence measured at 3.946.

The numerical-relativity evolver's accuracy falls out of grid refinement rather than being asserted: order 3.946 against the theoretical 4 on the standard Apples-with-Apples testbed. The same solver runs in your browser, with no cluster and no queue.

Try Live Open GDBS Lab Book an Enterprise Demo Download Free - Win x64
0.27%Hawking radiation error
across 60 orders of magnitude
0.345GeoNum drift shades
(well under 1.0)
10physics domains
browser-validated
140+HPC Lab modules
shipping

The cluster is where your physics goes to scale.
The browser is where your physics goes to get verified.

The economics

Where the money and the time actually go.

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.

Time to first result

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.

Cluster cost avoided

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.

Trust on every result

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.

Why now

This was not possible five years ago.

Three browser platform shifts matured at once, and GDBS adds the precision layer that makes them trustworthy for science and engineering.

WebAssembly

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.

WebGPU

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.

WebNN

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.

GeoNum drift tracking

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.

The Core Innovation

What the engine computes, and how it is checked.

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.

0.345
Shade drift on the Hawking-temperature chain spanning 10⁻³⁴ to 10⁻¹⁴, well under the 1.0 trust threshold; the result holds 0.27% accuracy vs the analytical closed form.
0.13%
Gravitational waves - reproduces LIGO's published GW150914 final black-hole mass, checked against Abbott et al. (LIGO/Virgo).
0.4696
Blasius boundary layer - the canonical flat-plate wall-shear value to within 0.002, checked against Falkner & Skan (1931).
Run the Theory Lab
GeoNum Precision

2048-shade zone/shade architecture. Drift compartments track error at every multiplication step - transparently, not silently.

Domain-Tuned Zones

One GeoNum class, domain-specific zone configurations. Theory, Quantum, Fluids, Plasma, Materials, Geophysics, Ballistics.

Seed-Based Storage

8-byte content addressing. 5D geometric positioning in semantic space. Automatic relationship discovery between data nodes.

Transparent Uncertainty

getUncertainty() and getRelativeUncertainty() on every result. No black box. Every computation auditable, every drift visible.

One geometric computing stack

One system. Three layers.

A unified geometric computing stack: precision, search, and reasoning. Precision (GeoNum) - Search (SyncSearch) - Reasoning (CORA), all on GDBS.

Powered by GDBS

C.O.R.A.

Coordinated Ontological Referencing Architecture

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.

Persistent GDBS memory - knowledge survives sessions
Domain-aware reasoning - physics, materials, geophysics
Native gdbsio engine - 4.7M-seed corpus, sub-10ms retrieval
Voice synthesis - natural TTS, hot-reload modules
Open C.O.R.A.
Protected by U.S. Patent App. No. 63/970,430
Powered by GDBS

SyncSearch

High-Speed Geometric Discovery Engine

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.

Sub-millisecond queries - no Java, no cluster overhead
90% cost reduction - vs Elasticsearch at comparable scale
Semantic + full-text - GDBS proximity + FTS5
Embeddable - single binary, add to any stack
Request Early Access
Protected by U.S. Patent App. No. 63/909,979
Powered by GDBS

GeoNum Engine

Drift-tracked precision, command line

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.

Drift-tracked - precision carried through the calculation, not assumed
Trust verdict - PRECISE / DRIFTING / UNRELIABLE / ERROR on every result
Single native binary - runs locally, no cluster, no service
3-day trial - then $60 / $4k / $8k per month, cancel anytime
Get GeoNum Engine Open
Protected by U.S. Patent App. No. 63/970,430
Validated Precision

Measured against published references.

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 Benchmarks
0.13%
Gravitational-Wave Merger

Reproduces 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.

3.946
Numerical Relativity

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.

0.27%
Hawking Temperature Precision

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.

$75k
vs $M/yr Cluster Time

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.

Benchmark Results

GDBS vs Published HPC Reference

Every result is reproducible in your browser. No cluster access required.

Benchmark GDBS Result Published Reference Error Source
GW150914 final black-hole mass 63.02 M☉ 63.1 M☉ 0.13% Abbott et al. (LIGO/Virgo), PRL 116
GW150914 final spin af 0.6855 0.69 0.65% Abbott et al. (LIGO/Virgo)
GW170817 chirp mass 1.185 M☉ 1.188 M☉ 0.3% Abbott et al. (LIGO/Virgo), PRL 119
Quantum chemistry (H₂, H₂O, CH₄) within tol. STO-3G HF 0.5-2% Szabo & Ostlund (textbook HF)
Blasius flat-plate wall shear f″(0) 0.4696 0.4696 <0.002 Falkner & Skan 1931 / Schlichting
Numerical relativity self-convergence order 3.946 4 (theorem) 4th-order Apples-with-Apples gauge testbed
Hawking temperature TH precision 0.27% analytical closed form 0.27% 60 orders of magnitude (10⁻³⁴-10⁻¹⁴), drift 0.345 shade
GPU constrained transport, |div B| 2.37e-4 < 2e-3 gate held Magnetized accretion torus, evolved on GPU

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.

Access Tiers

Start Free. Scale to Research.

From exploratory tools to full research workflows. No credit card required to start.

Free / Trial
Free

3-day full trial on signup. No credit card.

GDBS database
Theoretical Foundations
All modules (3 days)
Create Account
Academic
$99-$3.5k/yr

.edu required. Per 5 users. Student $99 · Faculty $249 · Lab $3,500.

All physics domains
HPC Lab + DFT Engine
Multi-physics coupling
Grant-friendly pricing
Student
.edu email required
$99/yr
Sign Up
Faculty / PI
.edu email required
$249/yr
Sign Up
Academic Lab
Grant-friendly · full platform
$3,500/yr
Sign Up
Standard / Pro / Enterprise
$2,083-$6,250/mo

Commercial physics modules, multi-physics coupling, SLA. HPC Lab + all addons on Enterprise. BSSN, LIGO, GRMHD sold as separate addons. ($25k-$75k/yr annual)

Standard / Pro physics domains
Multi-physics coupling + batch sweeps
Priority / dedicated support
Enterprise: HPC Lab + all addons + source code option
Standard
Standard physics domains
$2,083/mo or $25k/yr
Subscribe
Pro
+ Pro modules, dedicated support, SLA
$4,167/mo or $50k/yr
Subscribe
Enterprise
Premium SLA · commercial license · HPC Lab + all addons free
$6,250/mo or $75k/yr
Subscribe
Addons on Standard or Pro (included free with Enterprise):
· BSSN + Z4c (numerical relativity) - $5k/yr
· LIGO + NRSur (gravitational waves) - $5k/yr
· GRMHD (GR-MHD accretion) - $5k/yr
· All 3 bundle - $10k/yr (one free)
Source code* available to active Enterprise customers as a separate purchase.
* Enterprise-agreement-only: requires signed NDA and commercial agreement before purchase is enabled. Includes warranty terms, escrow option, on-site deployment support. Contact sales. Pricing subject to change at any time.
How it compares

GDBS vs Traditional Simulation Licensing

Tool License / yr Precision tracking Browser-accessible Cluster required
ANSYS Mechanical $50,000+ None No Often
COMSOL Multiphysics $15,000+ None No Optional
VASP (ab initio) $5,000+ academic None No Required
HPC Cluster Time $1M+/yr Post-hoc only No Is the cluster
GDBS Standard $25,000/yr Transparent drift Yes No
GDBS Enterprise $75,000/yr Transparent drift Yes No

Research Program

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.

Requirements:
· Institutional or academic affiliation
· Cite GDBS in any publications using results from the platform
· Share anonymised compute logs to improve precision validation
· Brief monthly check-in with the GDBS team

Academic and student pricing available - contact us directly. We respond to everything.

Apply for Access
Start Now

See the precision for yourself.

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.

Book an Enterprise Demo Open GDBS Theory Lab Download GDBS Free - Win x64

Prefer your calendar? Download a 30-minute hold (.ics) and we confirm the time by email.

Security & Trust

Your computational data never leaves your device.

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.

What stays on your device

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.

What we hold, and how we protect it

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.

AreaImplementation
Client-side computeEngines 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 transitTLS 1.2+ terminated at the edge; HSTS; no cleartext fallback.
Password storageBCrypt hashed (no plaintext, no reversible hash). Constant-time verify, including a dummy hash on unknown-user paths to prevent enumeration.
Session authJWT (HS256) with short-lived access token + refresh token; refresh enforces the disabled-account check; reset tokens are atomically consumed (single-use, race-free).
AuthorizationRole-based access control on all admin and investor endpoints; API keys capped to non-admin scope (admin actions require an interactive session).
Path / injectionStrict charset validation on collection identifiers; resolved paths verified inside the data root; GQL identifiers and string literals safely escaped; arXiv id regex-validated.
CORSExplicit allowlist (no AllowAnyOrigin); bearer tokens, no credentialed cookies.
Rate limitingPer-IP throttling on authentication and anonymous endpoints to deter credential stuffing and automated abuse.
Request size limitsBounded request bodies on compute and substrate endpoints; usage-log field lengths capped.
License keys128-bit entropy; constant-time comparison.
Payment dataStripe Checkout redirect; cardholder data never touches GDBS (SAQ-A shape, PCI-DSS).
Audit loggingAll API calls logged with session id, action, and timing; admin activity has a dedicated review surface.
HostingUS-based; TLS at the edge.

What we don't do

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.

Server-side features, disclosed plainly

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.

On formal attestations

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.

Service & support

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.

TierSupport commitment
EnterpriseContractual SLA per the EULA. Initial substantive response within 1 business day; dedicated success contact; custom SLA available on request.
ProContractual SLA per the EULA. Initial substantive response within 1 business day; priority handling.
Standard / PlusBest-effort priority handling, same 1-business-day response target on a commercially reasonable basis.
Academic / FreeStandard best-effort handling.

Documentation: EULA (PDF) · DUA (PDF) · Privacy. Additional documentation available under NDA - support@getvaultsync.com.

Get in touch

Talk to us.

Licensing, investment, integration - we answer fast. VaultSync Solutions Inc., Arkansas, USA.

Joe Garrett
Joe Garrett
Chief Executive Officer
Former Federal IT
Nique Carrington
Nique Carrington
Chief Operating Officer
Former Federal Director
Joanne Saberre
Joanne Saberre
Chief Legal Officer
Former Federal Counsel

Other VaultSync products

C.O.R.A. GeoNum Engine