Skip to main content
initializing...

    infrastructure

    where the run executes

    the services behind .bloom*: hosted compute, persisted provenance, and the boundaries that keep a scientific run connected to its result.

    infrastructure overview

    hosted compute, without managing a cluster.

    • cloud

      Enterprise-grade cloud platform with global CDN and auto-scaling.

    • security

      Encryption in transit and at rest, with audit trails; SOC 2 readiness in progress.

    • execution

      GPU and CPU workloads run through the hosted execution layer; completion time varies by tool and input.

    • storage

      Encrypted object storage for job results, with encrypted database backups.

    architecture

    two layers, and what they are built from.

    operational boundaries

    what depends on the tool, and what depends on the plan.

    • run time

      varies by tool

      execution time follows the selected workflow and input.

    • availability

      plan-dependent

      platform availability — contractual SLAs available on enterprise plans.

    • concurrency

      plan-dependent

      concurrent job capacity.

    • storage

      persistent

      data storage capacity.

    security & compliance

    the controls around a run.

    • encryption

      Data is encrypted in transit and at rest.

    • access control

      Role-based access control with fine-grained permissions.

      OAuth 2.0, JWT tokens, RBAC policies.

    • audit logging

      Audit logging for authenticated access and job activity.

      Structured logs, tamper-evident hash-chained storage, real-time monitoring.

    • infrastructure

      Secure cloud infrastructure with network isolation.

      VPC isolation, WAF protection, DDoS mitigation.

    for full certifications and compliance details, see compliance; for how your data is handled and how to report a vulnerability, see security.

    ready to try it out?

    one purpose: hypothesis to result, faster.

    Loading...