NexQloud Sovereign
A Covenant Cloud Partnership for Adventist digital infrastructure — owned, governed, and stewarded by the Church.
Own the infrastructure that carries the mission.
Not hosting. A way for the Seventh-day Adventist Church to own, govern, secure, and steward the digital infrastructure that carries its mission, protects its data, serves its institutions, and preserves its independence.
First — the part you came for.
You're here to vet how we secure it. Let's settle that first — then the bigger picture.
Independently audited.
SOC 2 Type 2
Unqualified opinion · Security criteria · audited by Prescient Security.
Zero incidents
No security incidents during or after the observation period.
unqualified opinion · Prescient Security
annual · independent third-party
in transit · at rest · TPM disk
MFA · least-privilege · PAM
You own it. We never see your data.
Locked down at every layer.
Zero Trust
Built on Nebula — every node gets a cryptographic identity; nothing is trusted by location.
Access
MFA enforced, least-privilege RBAC, privileged-access management, deprovision in ≤3 days.
Encryption
In transit and at rest (AWS KMS); TPM full-disk plus Lenovo/HP chassis-tamper on devices.
Who can decrypt your data? You.
AWS Secrets Manager (KMS)
Keys managed by NexQloud under IAM + RBAC — fit for our SOC 2-attested platform.
You hold the keys (HYOK)
Via our confidential-computing patents — no operator, including us, and no single cloud can decrypt it.
Continuously verified.
Monitoring
AWS GuardDuty threat detection, centralized logging, and a documented incident-response plan.
Testing
Quarterly vulnerability scans plus an annual third-party penetration test (VAPT).
Change / CI-CD
Dev / test / prod separation with documented approvals — change you can audit.
For 150 years the work was carried by property. Today it's carried by the cloud.
Churches, schools, hospitals, publishing houses — the Adventist Church secured them because they carry the mission. We never rented the ground the work stood on; we owned it, governed it, and held it in trust.
In the digital age, cloud infrastructure has become mission property. Member records, donor gifts, student and patient data, media, ministry — the front door to the mission is now digital. The question is the one the Church has always answered: do we own the ground the work stands on?
Owned for the cause of God — but never kingly power.
Ellen White urged the Church to secure its property for the cause of God, and organized in part to hold that property in trust for the work. Ownership was never the world's instinct to hoard — it was stewardship of what God had entrusted.
She also warned, just as firmly, against centralization — against "kingly power" gathered into one place. That gives us our design principle: the Church owns and governs the asset, while the architecture stays distributed, accountable, and regionally adaptable. Owned — but not over-centralized.
An institutional decision — not an IT purchase.
Six pillars.
Church-owned
Servers, data, identity, and recovery — owned by the Church. The new property.
Sovereign governance
Where data lives, who can open it, who holds the keys — decided by the Church.
Distributed, not central
Global standards, regional control, local resilience. Owned — never kingly power.
Trust-tier workloads
Sensitive data on high-assurance; everything else on low-cost capacity.
Mission continuity
Carries on through outage, censorship, lock-in, and attack. The lamp that doesn't go out.
Mission-aligned revenue
From expense to asset — infrastructure that helps fund the work.
Infrastructure that funds the work.
Once the Church owns secure, distributed infrastructure, it can responsibly extend it to mission-aligned organizations — faith-based schools, ministries, Christian media, and humanitarian and health initiatives that can't afford hyperscale cloud, without forcing them into the same dependency.
Like publishing houses and hospitals before it, the cloud becomes an institutional asset that both serves the mission and sustains it — revenue reinvested into education, healthcare, media, humanitarian work, and evangelism.
Five questions for the board.
Should the Church keep renting its most critical digital infrastructure — indefinitely?
Should member, donor, student, and patient data stay structurally dependent on outside hyperscalers?
Should we own the next generation of mission infrastructure — as we have owned churches, schools, and hospitals?
Can we reduce cloud cost while improving resilience, sovereignty, and global continuity?
Could this become the model for faith-based digital infrastructure worldwide?
A Covenant Cloud Design Partner.
Not a vendor contract — a joint institutional design partnership. We don't host the Church; we help the Church own its own cloud.
Sovereignty assessment
Map current spend, data sensitivity, residency, and the first workloads to move.
Pilot workloads
Start safe — public sites, media, backups — across a few countries. Live in 60–90 days.
Governance & expansion
Define who owns what and who holds the keys; then extend across the institutions.