GDBS (Geometric Database System) is a browser-native scientific computing SaaS platform. It delivers HPC-grade numerical precision across 8 physics domains using WebAssembly - no cluster, no installation, no job queue required. Every computation carries transparent drift and uncertainty tracking.

How does GDBS compare to ANSYS or COMSOL?

GDBS runs entirely in the browser via WebAssembly at a fraction of traditional simulation licensing costs. ANSYS Mechanical licenses start at $50,000+/yr with no browser access. COMSOL starts at $15,000+/yr per module. GDBS Standard starts at $25,000/yr ($2,083/mo) and Enterprise tops out at $75,000/yr ($6,250/mo), with 8 validated physics domains, transparent uncertainty tracking, no cluster requirement, and instant results - no job queue. HPC Lab is included with Enterprise. Numerical-relativity (BSSN + Z4c), gravitational-wave (LIGO + NRSur), and GR-MHD (GRMHD) addons are licensed separately at $5,000/yr each on Standard or Pro, and are included free with Enterprise.

Does GDBS require installation or a cluster?

No. GDBS runs entirely in the browser using WebAssembly (Wasm). No installation, no cluster, no GPU, no job queue. It works on any device - phone, laptop, or workstation - with identical precision results.

What physics domains does GDBS support?

GDBS includes 8 physics domains: Quantum (energy levels, H2 ground state), Fluids (CFD, Taylor-Green vortex), Plasma (Landau damping, MHD, tokamak stability), Materials (bulk modulus, crystal symmetry), Geophysics (gravitational field, seismology), Ballistics (hypersonic aerodynamics), Cosmology (galaxy rotation, CMB), and Molecular (drug screening, protein stability).

How accurate is GDBS compared to supercomputer results?

GDBS reproduces published scientific references where one exists: LIGO's GW150914 final black-hole mass to 0.13% and final spin to 0.65% (Abbott et al.), GW170817 chirp mass to 0.3%; quantum-chemistry energies within 0.5 to 2% of the Szabo and Ostlund reference; the Blasius boundary-layer value 0.4696 within 0.002; numerical-relativity self-convergence of order 3.946; a magnetized accretion torus on GPU holding magnetic-field divergence to 2.37e-4; and the analytic Hawking temperature to 0.27% across 60 orders of magnitude. Results are reproducible live in the browser.

Is there a free version of GDBS?

Yes. GDBS has a permanent free tier covering the GDBS database and Theoretical Foundations module (citation required). A 3-day full trial unlocks all physics domain modules with no credit card required. Academic plans start at $99/yr (per 5 users, .edu required). Commercial tiers are Standard ($25k/yr or $2,083/mo), Pro ($50k/yr or $4,167/mo), and Enterprise ($75k/yr or $6,250/mo). HPC Lab and the BSSN, LIGO and GRMHD addons are included free with Enterprise; on Standard or Pro each addon is $5k/yr, or $10k/yr for all three (one free). Pricing subject to change at any time.

GDBS | Scientific Computing SaaS - WebAssembly HPC Precision, Browser-Native

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.

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

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

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

HPC-grade precision at a fraction of cluster cost. Enterprise tops out at $75k/yr - full platform, HPC Lab, dedicated SLA. No job queue. Instant results. 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 a_f	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 T_H 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 HPC-grade 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

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

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

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.

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.

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.

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.

The database that
knows its own uncertainty.