Skip to main content

datafog

datafog core

Find and transform sensitive data in your application.

PyPI version npm version crates.io version Rust CI status MIT license

Quickstart · Detection · Transformations · Local models · Documentation

datafog core is a Rust library with Python, Node.js, and browser WebAssembly bindings. Scan text or JSON for personal data and credentials, then redact, mask, remove, pseudonymize, or tokenize matched values. Findings use a consistent format across the bindings.

Rule-based scanning runs locally without model weights or downloads. Optional local model sessions add datafog and GLiNER2 support in Rust, Python, and Node.js.

Stable: 1.4.0 · Release notes · Extension installation and testing.

Core 1.0 freezes Workspace contract 1 across Rust, Python, Node and browser WASM, with optional native/browser FogVault integrations. Snapshot v3 writes and v1/v2/v3 reads keep their existing semantics. Exact published 0.5.0-beta.3 interchange remains tested; FogVault is independently versioned 0.1.0.

Quickstart

Choose the exact 1.4.0 package for your application:

SDK Install 1.4.0 Requirements
Python python -m pip install datafog-core==1.4.0 Python 3.10+
Node.js npm install --save-exact @datafog/node@1.4.0 Node.js 24+
Rust cargo add datafog-core@=1.4.0 Rust 1.88+
Browser / WASM npm install --save-exact @datafog/wasm@1.4.0 Browser with WebAssembly support

Python

from datafog_core import scan, scan_and_transform

findings = scan("Email jane@example.com")
print(findings[0].entity_type)   # EMAIL
print(findings[0].matched_text)  # jane@example.com

result = scan_and_transform(
    "Email jane@example.com",
    {"transform": {"default": {"strategy": "redact"}}},
)
print(result.text)  # Email [EMAIL]
Node.js example
import { scan, scanAndTransform } from "@datafog/node";

const findings = scan("Email jane@example.com");
console.log(findings[0].entityType); // EMAIL
console.log(findings[0].matchedText); // jane@example.com

const result = scanAndTransform("Email jane@example.com", {
  transform: { default: { strategy: "redact" } },
});
console.log(result.text); // Email [EMAIL]
Rust example
use datafog_core::{
    scan, scan_and_transform, PrivacyError, ScanAndTransformConfig,
    TransformationConfig, TransformationStrategy,
};

fn main() -> Result<(), PrivacyError> {
    let findings = scan("Email jane@example.com");
    println!("{}", findings[0].entity_type); // EMAIL
    println!("{}", findings[0].matched_text); // jane@example.com

    let result = scan_and_transform(
        "Email jane@example.com",
        &ScanAndTransformConfig::new(TransformationConfig::new(
            TransformationStrategy::Redact,
        )),
    )?;
    println!("{}", result.text); // Email [EMAIL]
    Ok(())
}
Browser / WASM example
import { init, scan, scanAndTransform } from "@datafog/wasm";

await init();
console.log(scan("Email jane@example.com"));

const result = scanAndTransform("Email jane@example.com", {
  transform: { default: { strategy: "redact" } },
});
console.log(result.text); // Email [EMAIL]

Python and Node.js packages include prebuilt native binaries for Linux x64 and ARM64 (GNU), macOS Intel and Apple Silicon, and Windows x64 (MSVC).

Detection coverage

Coverage Entity types Activation
Personal and financial data EMAIL, PHONE, SSN, CREDIT_CARD, IP_ADDRESS, DATE, ZIP_CODE On by default
Credentials API_KEY, BEARER_TOKEN, JWT, PRIVATE_KEY, CREDENTIAL_URI On by default
Labeled street addresses STREET_ADDRESS On by default; bounded English street-line rule
Labeled accounts ACCOUNT_NUMBER On by default; bounded lexical rule
Labeled US identifiers US_ROUTING_NUMBER, NPI On by default; requires a supported text label
German identifiers IBAN, VAT ID, tax ID, social security number, postal code, passport number, residence permit number Explicit German locale
UUIDs UUID Explicit detect_uuid setting
Names in JSON fields PERSON Structured scans, using name-field aliases or explicit JSON Pointer mappings
Names and address blocks in prose PERSON, ADDRESS EmbeddedCnnDetector: weights compiled into the extension, no download or runtime
Caller-defined labels any GLiNER2 model sessions

Use structured scans to find names by JSON field, EmbeddedCnnDetector for recipient names and mailing-address blocks in prose, or model sessions for caller-defined labels.

Each finding includes its entity type, matched text, byte and code-point ranges, optional confidence, and detector name/version. Ranges are zero-based and end-exclusive. Node.js and WASM also provide UTF-16 ranges for JavaScript slice. Rule-based findings have no confidence score. Findings and ranges →

For scanning files from AI agents, use datafog MCP.

Detection settings
  • Select checks: scan(text, {"entities": ["EMAIL", "SSN"]}) in Python runs only the selected text detectors. Omit entities to use all enabled detectors. Selections must be nonempty, unique, exact entity names. Selecting a German type or UUID does not activate it; set locale or detect_uuid too.
  • German locale: {"locale": "de"} enables the seven German detectors. These use format/context rules; IBAN checksums and account existence are not verified. See the German reference for detector rules.
  • ENV and SQL: choose format: "env" or format: "sql" to handle email boundaries in assignments and quoted strings. Source-context rules →
  • Phone numbers: numbers without + use North American checks: ten digits, optionally preceded by 1, with area and exchange codes starting with 2–9. Numbers starting with + use a permissive 7–15 digit check, including shortened examples such as +1-555-1002. Country codes and assigned numbers are not validated; numeric identifiers can still match.
  • Decimal numbers and CSV: contiguous card digits after a digit and . or , are suppressed, so 3.4111111111111111 and 3,4111111111111111 do not produce card findings. Cards containing spaces or hyphens still undergo normal checks. Parse CSV/TSV into cells before scanning so delimiters and adjacent fields do not affect matching.

Use capabilities() in Rust or Python to discover supported entities and their activation rules.

Transformations

Strategy Result Application provider Browser / WASM
redact Replace with a label such as [EMAIL] None Supported
mask Replace characters, optionally revealing the first or last characters None Supported
remove Delete the matched span None Supported
pseudonymize Create a stable keyed HMAC-SHA-256 pseudonym Key provider Unsupported
tokenize Issue an opaque token that can be restored under the same scope Token provider Unsupported

Use transform with existing findings, or scan_and_transform / scanAndTransform to scan and transform together. Transformation records include source/output ranges and replacement metadata, without the original matched text.

Keep scan settings under scan and transformation policy under transform. A default strategy is required; entity selection, per-type overrides, and allowlists are optional. Configuration guide → · Strategy details →

Browser workspace and FogVault integration

The unreleased v1.1 browser extension flow adds a bundled, default-enabled name/address CNN with a disable control, plus SQLite3 Multiple Ciphers as a second encrypted Workspace backend. See the candidate integration guide.

Core 1.0 provides persistent Workspace pseudonyms, explicit approved saves, strict/progressive restoration, operation history and conversation-scoped recall. The optional browser adapter uses the maintained FogVault Worker/WASM owner and IndexedDB storage. Native Rust, Node and Python owners use the same portable vault core through the registered native adapter.

Install the browser integration:

npm install --save-exact @datafog/wasm@1.4.0 @datafog/fogvault-browser@0.1.0 @datafog/core-fogvault-browser@1.4.0

Integration guide and supported profiles → · Stable Workspace contract → · Model assets and runtime setup → · SDK release scope and separate extension acceptance →

Local models (beta)

Core 1.0 includes optional local sessions for the datafog PII model and GLiNER2 in Rust, Python and Node.js. Model files are provisioned separately; model quality measurements remain separate from SDK correctness.

Install the exact 1.4.0 SDK:

python -m pip install 'datafog-core==1.4.0'
npm install --save-exact @datafog/node@1.4.0
cargo add datafog-core@=1.4.0 --features models

For GLiNER2, install its optional dependencies in the Python environment used by the runner:

python -m pip install 'datafog-core[gliner2]==1.4.0'

Embedded name and address detection

EmbeddedCnnDetector carries the pinned statements-v1 CNN in the extension itself: no model download, no files, no subprocess and no inference runtime. It is the same detector the browser build embeds and returns the same ModelScanResult contract as ModelSession.

from datafog_core import EmbeddedCnnDetector

detector = EmbeddedCnnDetector()          # authenticates the embedded weights once
result = detector.scan(text, {"entities": ["PERSON", "ADDRESS", "EMAIL"]})

Limits are 65,536 input bytes and 8,192 tokens per request and 1,024 findings. Inference is synchronous and in-process, so ModelCancellation cannot interrupt it; keep a detector per worker thread. scan_model returns model-only findings, and EmbeddedCnnDetector.scan_disabled validates the same selection with no inference. Embedded CNN reference →

GLiNER2 supports the PII checkpoint and compatible general-purpose span models with caller-defined labels. The GLiNER2 runner ships in the Python package and also serves Node.js and Rust callers. Download and verify model files separately, then use ModelSession.open, text scan, and close. Reuse sessions across calls. Both backends return consistent results and errors, with cancellation and cleanup support.

datafog setup and session API → · GLiNER2 setup →

Documentation and development

For existing datafog Python applications, follow the migration guide for changes to imports, results, and transformations.

For Rust development, run:

cargo fmt --all --check
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo test --workspace --all-features

See the development guide for the repository layout and Python, Node.js, and WASM package checks.

License

MIT. Built by datafog.

Metadata

Release files for datafog-core 1.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for datafog-core 1.4.0
File Size Uploaded Provenance Actions
datafog_core-1.4.0.tar.gz 1.3 MB With provenance Details for datafog_core-1.4.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for datafog-core 1.4.0
File Actions
datafog_core-1.4.0-cp310-abi3-win_arm64.whl CPython 3.10 abi3 Windows ARM64 Details for datafog_core-1.4.0-cp310-abi3-win_arm64.whl
datafog_core-1.4.0-cp310-abi3-win_amd64.whl CPython 3.10 abi3 Windows x86-64 Details for datafog_core-1.4.0-cp310-abi3-win_amd64.whl
datafog_core-1.4.0-cp310-abi3-musllinux_1_2_x86_64.whl CPython 3.10 abi3 Linux musl 1.2+ x86-64 Details for datafog_core-1.4.0-cp310-abi3-musllinux_1_2_x86_64.whl
datafog_core-1.4.0-cp310-abi3-musllinux_1_2_aarch64.whl CPython 3.10 abi3 Linux musl 1.2+ ARM64 Details for datafog_core-1.4.0-cp310-abi3-musllinux_1_2_aarch64.whl
datafog_core-1.4.0-cp310-abi3-manylinux_2_28_x86_64.whl CPython 3.10 abi3 Linux glibc 2.28+ x86-64 Details for datafog_core-1.4.0-cp310-abi3-manylinux_2_28_x86_64.whl
datafog_core-1.4.0-cp310-abi3-manylinux_2_28_s390x.whl CPython 3.10 abi3 Linux glibc 2.28+ IBM System/390x Details for datafog_core-1.4.0-cp310-abi3-manylinux_2_28_s390x.whl
datafog_core-1.4.0-cp310-abi3-manylinux_2_28_ppc64le.whl CPython 3.10 abi3 Linux glibc 2.28+ PowerPC 64-le Details for datafog_core-1.4.0-cp310-abi3-manylinux_2_28_ppc64le.whl
datafog_core-1.4.0-cp310-abi3-manylinux_2_28_aarch64.whl CPython 3.10 abi3 Linux glibc 2.28+ ARM64 Details for datafog_core-1.4.0-cp310-abi3-manylinux_2_28_aarch64.whl
datafog_core-1.4.0-cp310-abi3-macosx_11_0_arm64.whl CPython 3.10 abi3 macOS 11.0+ ARM64 Details for datafog_core-1.4.0-cp310-abi3-macosx_11_0_arm64.whl
datafog_core-1.4.0-cp310-abi3-macosx_10_12_x86_64.whl CPython 3.10 abi3 macOS 10.12+ x86-64 Details for datafog_core-1.4.0-cp310-abi3-macosx_10_12_x86_64.whl

Total release size: 35.8 MB

Release files / datafog_core-1.4.0.tar.gz

Download URL datafog_core-1.4.0.tar.gz
Size 1.3 MB
Tags Source
SHA-256 checksum
How to use checksums
092c5c7981d4b816df4fbc83c9c03af37f480aeb24bc77d9497d83acb1c12ca5
BLAKE2b-256 checksum
How to use checksums
8039ff7f3706e512adf53ebe0e97167b91cdad50405495ebc007e7ad34bc0f9c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

Release files / datafog_core-1.4.0-cp310-abi3-win_arm64.whl

Download URL datafog_core-1.4.0-cp310-abi3-win_arm64.whl
Size 3.0 MB
Tags CPython 3.10 Windows ARM64 abi3
SHA-256 checksum
How to use checksums
be0cda988686bde907d4e9dc42d547e2baebb895da945d1110974df4ea0b42f0
BLAKE2b-256 checksum
How to use checksums
33dcfcdcca3b6810e8d14d712eedc90c4e4d391b3ce6c4a8e2fe523dfeba0f1c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

Release files / datafog_core-1.4.0-cp310-abi3-win_amd64.whl

Download URL datafog_core-1.4.0-cp310-abi3-win_amd64.whl
Size 3.1 MB
Tags CPython 3.10 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
ceb35d4c168784a8a4ca1ac17079849feda42ba5f71021027856e1ca50249c81
BLAKE2b-256 checksum
How to use checksums
a57638bbb39407534c794ad8feee1e7b5428a562c66f598444efd008caf9566d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

Release files / datafog_core-1.4.0-cp310-abi3-musllinux_1_2_x86_64.whl

Download URL datafog_core-1.4.0-cp310-abi3-musllinux_1_2_x86_64.whl
Size 3.8 MB
Tags CPython 3.10 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
c6939f07ad87fcbc5d2bd790a8c845b012d56616655ec61c857d51289889b737
BLAKE2b-256 checksum
How to use checksums
d1461e9aaafcab6f67be98eb387a29a04fe2b9fb7c0dbc8d5d800960eb6c17b5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

Release files / datafog_core-1.4.0-cp310-abi3-musllinux_1_2_aarch64.whl

Download URL datafog_core-1.4.0-cp310-abi3-musllinux_1_2_aarch64.whl
Size 3.6 MB
Tags CPython 3.10 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
c74ba926f0a4abb0022ba137e90e2028576c895ac9c85cab27f16a725b9b2c3c
BLAKE2b-256 checksum
How to use checksums
85f826018c2a4b9e3ce531469d0413fba71ce21dae9204c18770081679148d06
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

Release files / datafog_core-1.4.0-cp310-abi3-manylinux_2_28_x86_64.whl

Download URL datafog_core-1.4.0-cp310-abi3-manylinux_2_28_x86_64.whl
Size 3.6 MB
Tags CPython 3.10 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
c383e02c866d7f8facf660dd91b5c855e008d02c43488a4c57f4644459bb150a
BLAKE2b-256 checksum
How to use checksums
67e27b1c052748a12695e882009fec96253dcd16b26b625181a1cf2847bd45bb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

Release files / datafog_core-1.4.0-cp310-abi3-manylinux_2_28_s390x.whl

Download URL datafog_core-1.4.0-cp310-abi3-manylinux_2_28_s390x.whl
Size 3.5 MB
Tags CPython 3.10 Linux glibc 2.28+ IBM System/390x abi3
SHA-256 checksum
How to use checksums
94eb3c3ff6dd1ff72a77f678a6b1f6978994f8c70ef10e475586b47ed9ea3cdf
BLAKE2b-256 checksum
How to use checksums
1fb024e2eaae067b2045dea5807e1f39967b409f6b964164af2bad4f47d357d5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

Release files / datafog_core-1.4.0-cp310-abi3-manylinux_2_28_ppc64le.whl

Download URL datafog_core-1.4.0-cp310-abi3-manylinux_2_28_ppc64le.whl
Size 3.8 MB
Tags CPython 3.10 Linux glibc 2.28+ PowerPC 64-le abi3
SHA-256 checksum
How to use checksums
788d16a6ce75b8187a3c9aba9dd03ea928a6865db3c46c4ceaf67d046a33b365
BLAKE2b-256 checksum
How to use checksums
ca181211b62923f28517f89f065062a98d53ae6e815ca2e26029cca27065f3a1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

Release files / datafog_core-1.4.0-cp310-abi3-manylinux_2_28_aarch64.whl

Download URL datafog_core-1.4.0-cp310-abi3-manylinux_2_28_aarch64.whl
Size 3.5 MB
Tags CPython 3.10 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
4c3d5b55542a28191f7ef0b3f86ac488f201abb45ae8628fabd7030e12e33d45
BLAKE2b-256 checksum
How to use checksums
a95e0b89b32b94cb7b9a6f83bb965230a3a0d1a796b345ca24598b098b396bb0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

Release files / datafog_core-1.4.0-cp310-abi3-macosx_11_0_arm64.whl

Download URL datafog_core-1.4.0-cp310-abi3-macosx_11_0_arm64.whl
Size 3.3 MB
Tags CPython 3.10 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
16392d1d741f93cca00f68777ea41d60fd297a839e89bd4e70fcd94b414633ee
BLAKE2b-256 checksum
How to use checksums
09f76fc9c83986d520d42a8cec1cae38d4c20d1b9c63719007b69b479fbd864f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

Release files / datafog_core-1.4.0-cp310-abi3-macosx_10_12_x86_64.whl

Download URL datafog_core-1.4.0-cp310-abi3-macosx_10_12_x86_64.whl
Size 3.4 MB
Tags CPython 3.10 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
4b357c23e1dca2839da48dc084e4366160f924db074bd9753e8a8e5f86667530
BLAKE2b-256 checksum
How to use checksums
93dab5d094ecc1e2f8f71805408870df93cabac201f1babb4308532bf4142208
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

Security for datafog-core 1.4.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 11 files in this release have been uploaded with provenance metadata.

Select from 11 files

Attestation for datafog_core-1.4.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.4.0 This release

11 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page