BYODB — BRING YOUR OWN DATABASE

Bring Your Own
MongoDB Atlas

Your cluster. Your region. Your control.

Provision your Atlas cluster before onboarding. Forescribe connects with read and write scope — your data never moves.

SOC 2 Type II

TLS 1.3

Read & write scope

Zero egress

MongoDB Atlas

Customer-provisioned cluster

LIVE

REGION

us-east-1

N. Virginia

CLUSTER

M30 / 3× nodes

AES-256 at rest

REPLICA SET

Primary

●●●

Secondary

●●●

Arbiter

●●●

Customer-ownedLogically isolatedNo comminglingRead-write scope

Forescribe connectionTLS 1.3

ACT 1- FOUNDATION

Built on customer owership

Three principles that are structural-not configurable.

Customer-owned

Your Atlas account. Your billing. Your admin keys.

Region-selected

You choose the data center. We never override.

No commingling

Cluster-level isloation. Not a policy-structural.

ACT 2- SETUP

Connected before onboarding.

Your cluster exists and is running before Forescribe
touches anything.

STEP 01of 5

Provision your cluster

You create the Atlas cluster in your own MongoDB account.

Your Atlas account, your billing

Choose M10 → M60+ tier

Multi-cloud optional

Manual Mode

ATLAS CLUSTER

ACT 3 — ARCHITECTURE

Clear boundaries, by design.

Your data stays in your region. We zoom in to prove it.

us-east-1

N. Virginia · US · Data stays here

Map

Customer Boundary

N. Virginia · US

MongoDB Atlas

🗄️

Your Data

AES-256 at rest

🔑

Admin credentials

Customer-owned

📍

us-east-1

Pinned region

FORESCRIBE BOUNDARY

CENTRAL CONTROL

Control plane

📋

Read & Write Access

Allows both data queries

📰

Audit pipeline

Immutable, in your cluster

📃

Zero data stored

We hold no copy

Atlas

us-east-1

🔒

Forescribe

Read and write

TLS 1.3 enforced

mTLS verified

Read-write scope

ACT 4 — CONTROLS

Engineered for enterprise trust.

Five structural guarantees. Each visualised below.

CUSTOMER A

Collection A1

Collection A2

Collection A3

CUSTOMER B

Collection B1

Collection B2

Collection B3

HARD BOUNDARY

Logical isolation

Every customer gets a dedicated cluster namespace. This isn't a policy setting — it's architectural. Your data and another customer's data can never coexist in the same cluster.

ACT 5- CTA

Own the database.
Keep the control.

Nothing moves. Nothing shared.

SOC 2 Type II

TLS 1.3

Read & write scope

Zero egress

ACT 6- FAQ

Frequently asked questions

Everything you need to know about us.

Overview

Data Control

Access & Permissions

Data Writes

What does “Bring Your Own Database” mean?

When is the database set up?

Subscribe to Forescribe Monthly

The latest news and updates from Forescribe, sent to your inbox.

Step into the future of Software GovernanceSimpler, smarter, and built for today’s digital-first teams.

Empowering digital-first enterprises to elevate Procurement, IT, and FinOps, through precision-driven SAM and Autonomous Software Governance excellence.