Skip to main content
Servers Are Up
Virtual Datacenter
PricingFree Tools
Sign inBrowse catalog
Servers Are Up
Virtual Datacenter
PricingFree Tools
Sign inBrowse catalog
Servers Are Up

Your apps, automation and data on hardware we own. Build a private stack with predictable capacity and access through your dashboard, API or SSH.

SLA with service creditsOwned hardwareUS-based

Make room for your next idea

Explore the capacity, apps and access options that fit your workload. Check current availability and your total before you buy.

Sign up freeView Pricing

Products

  • Linux VPS
  • Windows VPS
  • Cloud & SaaS Services
  • Cloud Storage (Azure)
  • Virtual Datacenter
  • AI & Agent Hosting
  • Containers
  • Instant Apps
  • Software Platforms
  • Network builder
  • Game Servers
  • Pricing

Resources

  • Free Network Tools
  • 2026 Pricing Benchmark
  • Live SVG Badges
  • Latency & Speed Test
  • Guides & Tutorials
  • Documentation
  • API Reference
  • MCP Server
  • CLI & SDKs
  • OpenAPI & llms.txt
  • Use Cases
  • Free Migration
  • Uptime & Reliability
  • Datacenter
  • System Status
  • Network
  • Provider Comparisons Hub
  • Compare Providers

Company

  • About Us
  • Enterprise
  • Security Architecture
  • Trust Center
  • Blog
  • FAQ
  • Compliance
  • Startup Program
  • Open-Source Sponsorship
  • Press & Media Kit
  • Referral Program
  • Help Center
  • Contact Us
© Servers Are Up
TermsPrivacySLARefund PolicyDPAAcceptable Use
Service information
Back to Engineering BlogCloud Platform & Storage
Cloud Platform Architecture Team·Published 2026-11-14·9 min read·Technical Review Verified

Building Zero-Trust Stateful Apps Without Hyperscaler Lock-In: Inside SAU Multi-Model Cloud DB, ES256 OIDC, Key Vault & Cloud SIEM

cloud-database pgvector oidc zero-trust key-vault siem serverless

Engineering Summary & Direct Answer

Architectural deep dive into ServersAreUp’s first-party 112-service Cloud Platform (/cloud): combining JSONB + SQL + pgvector HNSW search with ETag concurrency, ES256 OIDC & ZTNA identity, Key Vault KMS envelope cryptography, AMD SEV-SNP enclaves, and MITRE ATT&CK SIEM playbooks.

Instant 60s deploy · Browser SSH & WebRDP included
Explore Cloud Storage Browse All Cloud ServicesVirtual Datacenter Pools ($12–$380/mo)
On this page (6 sections)
  1. Escaping the Five-Vendor SaaS Tax Without Falling Into Hyperscaler Lock-In
  2. Architectural Overview of Core First-Party SAU Cloud Primitives
  3. 1. SAU Multi-Model Cloud Database (/api/v1/cloud-db): Five Data Models, Five Consistency Levels & ETag Concurrency
  4. 2. SAU Cloud Identity (/dashboard/identity): ES256 OIDC JWKS, SCIM 2.0, PIM JIT & Clientless ZTNA
  5. 3. SAU Key Vault KMS (/api/v1/vault), Cloud SIEM (/dashboard/sentinel) & AMD SEV-SNP Enclaves
  6. Envelope KMS & Dynamic Database Leases (/api/v1/vault)
  7. SAU Cloud SIEM & SOAR (/dashboard/sentinel)
  8. Serverless Functions (400,000 GB-sec/mo Free) & AMD SEV-SNP Confidential Enclaves

Escaping the Five-Vendor SaaS Tax Without Falling Into Hyperscaler Lock-In

Shipping a modern, compliance-ready AI or B2B SaaS application in 2026 usually forces engineering teams into one of two traps: either stitching together five separate usage-metered startups (one for SQL, one for vector search, one for OIDC/SCIM auth, one for KMS secrets, and one for SIEM logs), or surrendering to proprietary hyperscaler IAM/SDK lock-in where egress fees and opaque billing units punish growth.

We built the first-party ServersAreUp 112-Service Cloud & Managed SaaS Platform (/cloud & /dashboard/cloud-services) around open wire standards (OIDC 1.0, SCIM 2.0, JSON-RPC, standard REST, SQL, pgvector, and OTLP) and transparent unit economics—so your team can compose Multi-Model Cloud Databases, Zero-Trust Identity, Key Vault KMS, Cloud SIEM & SOAR, Serverless Functions, and AMD SEV-SNP Confidential Enclaves alongside dedicated OpenStack KVM servers without vendor lock-in.

Below is the reference architecture and real production code for wiring these core primitives together.


Architectural Overview of Core First-Party SAU Cloud Primitives

SAU Cloud Service Dashboard & API Endpoint Core Engineering Capabilities Free Tier & Predictable Pricing
SAU Multi-Model Cloud Database /dashboard/cloud-db · /api/v1/cloud-db Unified JSONB documents + relational SQL + key-value + property graph + pgvector HNSW cosine similarity, 5 consistency levels, ETag If-Match concurrency & change-feed streams 100,000 RU/mo free · then \$0.25 / 1M RU
SAU Cloud Identity /dashboard/identity Multi-tenant OIDC 1.0 (ES256 JWKS), SCIM 2.0 directory sync, PIM Just-In-Time (JIT) role elevation & clientless ZTNA reverse proxy Included developer tenants + flat org tiers
SAU Key Vault KMS /dashboard/key-vault · /api/v1/vault Envelope wrap/unwrap cryptography, automated secret rotation & short-lived dynamic database credentials Metered transparently per 10k KMS ops
SAU Cloud SIEM & SOAR /dashboard/sentinel Real-time security event ingestion, MITRE ATT&CK rule correlation & automated containment playbooks Integrated across SAU compute, identity & APIs
SAU Serverless Functions & Enclaves /dashboard/cloud-services Event-driven HTTP/cron functions + hardware memory-encrypted AMD SEV-SNP Confidential Enclaves 400,000 GB-sec/mo free compute grant

1. SAU Multi-Model Cloud Database (/api/v1/cloud-db): Five Data Models, Five Consistency Levels & ETag Concurrency

Running separate operational databases for relational transactions, flexible JSON user state, session key-value caches, entity graphs, and 1536-dimensional AI embeddings multiplies connection pools and creates race conditions whenever a webhook updates SQL before your external vector index re-indexes.

SAU Multi-Model Cloud Database (/dashboard/cloud-db, /api/v1/cloud-db) executes all five workloads inside a single transactional engine:

  1. Multi-Model Execution: Query structured SQL tables, index schema-agile JSONB document collections, execute sub-millisecond Key-Value point reads, traverse Graph adjacency edges, and run pgvector HNSW (Hierarchical Navigable Small World) approximate nearest-neighbor cosine similarity searches in one hybrid filter query—so tenant RBAC predicates (tenant_id = $1) filter vectors during graph traversal rather than post-filtering leaked candidates!
  2. Five Tunable Read Consistency Levels: Select per-container or per-request semantics across Strong (linearizable quorum reads for financial balances), Bounded Staleness (lag bounded by K versions or T milliseconds), Session (monotonic read-your-own-writes per client session token—ideal default for web & AI apps), Consistent Prefix (never observes out-of-order writes), and Eventual (lowest-RU geo-replicated analytics reads).
  3. Lock-Free Optimistic Concurrency via ETag + If-Match: Every document and row carries a cryptographic version ETag. When two autonomous AI agents or concurrent webhook workers read version "v42" and race to update state, passing If-Match: "v42" ensures the first commit wins (v43) while the second receives 412 Precondition Failed immediately—preventing silent lost updates without holding pessimistic database locks across slow LLM calls!
  4. Ordered Change-Feed Streams: Subscribe serverless functions or background workers to an ordered append-only stream of committed mutations for real-time audit, cache invalidation, or embedding enrichment—starting with 100,000 RU/mo free and scaling linearly at \$0.25 per 1M Request Units (RU).
// Hybrid pgvector HNSW semantic search + ETag If-Match atomic state mutation (/api/v1/cloud-db)
const SAU_API = 'https://serversareup.com/api/v1/cloud-db';

export async function searchTenantKnowledgeAndClaimTask(
  token: string,
  tenantId: string,
  queryEmbedding: number[],
  taskId: string,
) {
  // 1. Hybrid JSONB metadata filter + pgvector HNSW cosine similarity in a single Session-consistent query
  const searchRes = await fetch(`${SAU_API}/collections/agent_knowledge/query`, {
    method: 'POST',
    headers: {
      Authorization: `Bearer ${token}`,
      'Content-Type': 'application/json',
      'X-SAU-Consistency-Level': 'Session',
    },
    body: JSON.stringify({
      filter: { tenantId, status: 'published' },
      vectorSearch: {
        field: 'embedding',
        vector: queryEmbedding,
        metric: 'cosine',
        topK: 5,
        efSearch: 64,
      },
    }),
  });
  if (!searchRes.ok) throw new Error(`Cloud DB search failed: ${searchRes.status}`);
  const { items, ruCharge } = await searchRes.json();

  // 2. Read task document + capture its current ETag
  const docRes = await fetch(`${SAU_API}/collections/agent_tasks/items/${taskId}`, {
    headers: { Authorization: `Bearer ${token}`, 'X-SAU-Consistency-Level': 'Strong' },
  });
  const etag = docRes.headers.get('etag');
  const taskDoc = await docRes.json();

  // 3. Conditional atomic write: fails safely with HTTP 412 if another worker mutated taskDoc!
  const updateRes = await fetch(`${SAU_API}/collections/agent_tasks/items/${taskId}`, {
    method: 'PUT',
    headers: {
      Authorization: `Bearer ${token}`,
      'Content-Type': 'application/json',
      'If-Match': etag ?? '*',
    },
    body: JSON.stringify({
      ...taskDoc,
      state: 'claimed',
      contextDocIds: items.map((d: { id: string }) => d.id),
      claimedAt: new Date().toISOString(),
    }),
  });

  if (updateRes.status === 412) {
    throw new Error('CONCURRENCY_CONFLICT: Another agent claimed this task first.');
  }
  return { matchedDocs: items, searchRuCharge: ruCharge };
}

2. SAU Cloud Identity (/dashboard/identity): ES256 OIDC JWKS, SCIM 2.0, PIM JIT & Clientless ZTNA

Hardcoding shared JWT HS256 symmetric secrets across twenty microservices means any compromised edge worker can forge arbitrary admin tokens for every other service.

SAU Cloud Identity (/dashboard/identity) issues standard OpenID Connect 1.0 (OIDC) tokens signed asymmetrically with Elliptic Curve P-256 (ES256) private keys inside hardware-protected key stores while publishing public verification keys at your tenant's standard JWKS discovery endpoint:

  • SCIM 2.0 Automated Lifecycle Provisioning: When HR deactivates a departing contractor in your corporate directory, SCIM 2.0 immediately revokes active refresh sessions, group memberships, and console entitlements in sub-seconds.
  • Privileged Identity Management (PIM) Just-In-Time (JIT) Elevation: Production engineers operate day-to-day with zero standing destructive privileges (viewer role), requesting a time-boxed (1h–4h), MFA-verified, audit-logged PIM elevation with ticket justification only when diagnosing a live incident.
  • Clientless Zero-Trust Network Access (ZTNA) Proxy: Publish internal staging apps, Grafana dashboards, or admin panels behind /dashboard/identity ZTNA policies—verifying ES256 OIDC identity, WebAuthn passkey posture, and device context on every HTTP request before forwarding over private SDN without installing VPN clients on contractor laptops.

Verify incoming SAU Cloud Identity ES256 JWTs in any TypeScript, Edge, or Node.js backend using standard WebCrypto (jose) with zero vendor SDK lock-in:

// Zero-lock-in OIDC ES256 JWKS verification using standard WebCrypto ('jose')
import { createRemoteJWKSet, jwtVerify } from 'jose';

const TENANT_ISSUER = 'https://serversareup.com/oidc/tenants/org_prod_92a';
const JWKS = createRemoteJWKSet(new URL(`${TENANT_ISSUER}/.well-known/jwks.json`));

export async function verifyZeroTrustRequest(bearerToken: string) {
  const { payload, protectedHeader } = await jwtVerify(bearerToken, JWKS, {
    issuer: TENANT_ISSUER,
    audience: 'api://billing-core-prod',
    algorithms: ['ES256'], // Strictly reject 'none' or symmetric HS256 downgrade attacks!
    clockTolerance: '5s',
  });

  return {
    subject: payload.sub,
    orgId: String(payload['org_id']),
    roles: (payload['roles'] as string[]) ?? [],
    jitElevatedUntil: payload['pim_exp'] ?? null,
    kid: protectedHeader.kid,
  };
}

3. SAU Key Vault KMS (/api/v1/vault), Cloud SIEM (/dashboard/sentinel) & AMD SEV-SNP Enclaves

Completing a zero-trust architecture requires eliminating static credentials on disk, protecting memory in use, and automating intrusion response:

Envelope KMS & Dynamic Database Leases (/api/v1/vault)

Instead of storing long-lived database credentials or raw master encryption keys in environment variables, applications call /api/v1/vault at boot to unwrap Data Encryption Keys or lease short-lived dynamic database credentials that automatically expire and drop their SQL role when the worker terminates:

# 1. Envelope-wrap a local 32-byte DEK using a non-exportable Vault KEK
curl -fsSL -X POST https://serversareup.com/api/v1/vault/keys/kek-payments-v3/wrap \
  -H "Authorization: Bearer ${SAU_WORKLOAD_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{"algorithm":"AES-256-GCM","plaintextBase64":"'"$(openssl rand -base64 32)"'"}'

# 2. Request a 1-hour dynamic read/write database credential lease (zero static DSN secrets!)
curl -fsSL -X POST https://serversareup.com/api/v1/vault/leases/database/orders-prod \
  -H "Authorization: Bearer ${SAU_WORKLOAD_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{"role":"app_rw","ttlSeconds":3600}'

SAU Cloud SIEM & SOAR (/dashboard/sentinel)

Every OIDC login anomaly, PIM elevation, Key Vault unwrap call, Cloud DB administrative mutation, and Linux/Windows host security log flows into SAU Cloud SIEM & SOAR (/dashboard/sentinel). Built-in correlation rules map multi-stage behavior directly to the MITRE ATT&CK matrix (such as impossible-travel token replay T1078 followed by unusual bulk secret unwrapping T1552) and trigger automated SOAR containment playbooks: revoking the session's OIDC refresh family, expiring dynamic Vault leases immediately, and quarantining the offending IP across edge nftables sets in under two seconds.

Serverless Functions (400,000 GB-sec/mo Free) & AMD SEV-SNP Confidential Enclaves

For bursty webhook handlers, Cloud DB change-feed consumers, and SIEM SOAR remediation hooks, SAU Serverless Functions include 400,000 GB-sec/mo free so event-driven glue code costs \$0 at baseline. And for regulated healthcare, fintech, or proprietary AI weights where sensitive data must remain encrypted even in physical RAM during CPU execution, SAU Confidential Enclaves leverage AMD SEV-SNP (Secure Encrypted Virtualization — Secure Nested Paging) silicon memory encryption with cryptographic remote attestation—verifying exact enclave measurement hashes before Key Vault releases decryption keys!

Explore all 112 first-party cloud services on /cloud or provision your first 100,000 RU/mo free Cloud Database in /dashboard/cloud-db.


Frequently Asked Questions

How does SAU Multi-Model Cloud Database prevent vendor lock-in while supporting five data models?

Unlike proprietary cloud NoSQL engines that require custom query languages, SAU Multi-Model Cloud Database (/dashboard/cloud-db) builds on open JSON, relational SQL, and pgvector HNSW cosine similarity standards exposed over clean HTTP/JSON (/api/v1/cloud-db), with 100,000 RU/mo free and transparent \$0.25 / 1M RU scaling.

Why use HTTP ETag and If-Match headers instead of database row locks for AI agents?

Autonomous agents often spend 3 to 20 seconds calling external APIs between reading state and writing updates. Holding pessimistic SQL transaction locks across external HTTP calls exhausts connection pools quickly, whereas optimistic If-Match ETag checks scale lock-free and deterministically reject stale concurrent overwrites with HTTP 412.

How do SAU Cloud Identity, Key Vault KMS, and Cloud SIEM work together during a credential incident?

Workloads authenticate with short-lived ES256 OIDC tokens (/dashboard/identity) to lease dynamic secrets from Key Vault (/api/v1/vault). If Cloud SIEM (/dashboard/sentinel) correlates an anomalous MITRE ATT&CK access pattern, an automated SOAR playbook revokes both the OIDC token session and the dynamic Vault database lease immediately.

What workloads benefit most from AMD SEV-SNP Confidential Enclaves vs Serverless Functions?

Use Serverless Functions (400,000 GB-sec/mo free) for stateless webhooks, cron jobs, and Cloud DB change-feed workers. Choose AMD SEV-SNP Confidential Enclaves when processing PII, PCI payment payloads, HIPAA records, or proprietary cryptographic keys that require hardware-encrypted guest RAM and remote cryptographic attestation.

SAU Cloud Platform (117 Services) & Azure-Hosted Blob Storage

Deploy Managed Cloud Storage & Multi-Model Cloud Databases

Start with 5 GiB free Azure-hosted Cloud Blob Storage ($9/mo for 250 GiB ZRS, $29/mo for 1 TiB GRS with double AES-256-GCM + Azure SSE encryption & WORM locks) plus 100K RU/mo free Multi-Model Cloud DB.

Explore Cloud Storage Browse All Cloud Services

Explore With AI & Cite This Page

Open a grounded prompt in your AI assistant or copy a clean Markdown, HTML, or APA reference link.

Ask ChatGPT Ask Perplexity Ask Claude
Share:HN·Reddit·X·LinkedIn
Newer Article

Inside Managed Cloud Storage on ServersAreUp: Client-Side AES-256-GCM Double-Envelope Encryption, Azure Geo-Redundancy & WORM Immutability

Older Article

AI Infrastructure Management: Deterministic Control Planes, MCP Tooling, and Stateful Agent Fleets

Related Diagnostic Tools & Engineering Guides

Validate protocols and subnets directly in your browser or continue reading related architecture notes.

Free Browser Tool

SSH Keygen Generator & Cloud-Init YAML Builder

Launch utility
Free Browser Tool

Cloud Cost & Infrastructure ROI Calculator

Launch utility
Free Browser Tool

Free DNS Zone File, CAA & DMARC Record Generator

Launch utility

Zero-Daemon Operator Toolbox, 1-Click Self-Hosted Apps & Managed Cloud SaaS Architecture (2026)

Inside ServersAreUp’s four-tier software and SaaS architecture: the zero-daemon Operator Toolbox (AES-256-GCM burn-after-reading secrets, WebRTC P2P file relay, TOTP/JWT & DNS/HMAC labs), 69 free Linux VPS Docker installers, 105 Instant Apps, and 112 Cloud offerings.

On this page

  1. Escaping the Five-Vendor SaaS Tax Without Falling Into Hyperscaler Lock-In
  2. Architectural Overview of Core First-Party SAU Cloud Primitives
  3. 1. SAU Multi-Model Cloud Database (/api/v1/cloud-db): Five Data Models, Five Consistency Levels & ETag Concurrency
  4. 2. SAU Cloud Identity (/dashboard/identity): ES256 OIDC JWKS, SCIM 2.0, PIM JIT & Clientless ZTNA
  5. 3. SAU Key Vault KMS (/api/v1/vault), Cloud SIEM (/dashboard/sentinel) & AMD SEV-SNP Enclaves
  6. Envelope KMS & Dynamic Database Leases (/api/v1/vault)
  7. SAU Cloud SIEM & SOAR (/dashboard/sentinel)
  8. Serverless Functions (400,000 GB-sec/mo Free) & AMD SEV-SNP Confidential Enclaves
  • Frequently Asked Questions
  • How does SAU Multi-Model Cloud Database prevent vendor lock-in while supporting five data models?
  • Why use HTTP ETag and If-Match headers instead of database row locks for AI agents?
  • How do SAU Cloud Identity, Key Vault KMS, and Cloud SIEM work together during a credential incident?
  • What workloads benefit most from AMD SEV-SNP Confidential Enclaves vs Serverless Functions?
  • LDAPS Port 636 vs. StartTLS 389: TLS 1.3 Hardening, Channel Binding & Cloud Identity Migration

    Engineering guide to LDAPS TCP port 636 vs LDAP StartTLS port 389: downgrade risks, TLS 1.3 cipher suites, X.509 SAN hostname validation, AD Channel Binding (CBT), ldapsearch diagnostics, and migrating to OIDC & SCIM 2.0.

    Enterprise SAML 2.0 & OIDC Engineering Guide: XML Signature Wrapping (XSW), PKCE S256 & ES256 JWKS

    Deep protocol and security guide to SAML 2.0 and OpenID Connect (OIDC) SSO with Entra ID, Okta, and Google Workspace: defending against XML Signature Wrapping (XSW) and XXE, implementing OIDC PKCE (S256) + ES256 JWKS rotation, and troubleshooting clock skew.

    Inside Managed Cloud Storage on ServersAreUp: Client-Side AES-256-GCM Double-Envelope Encryption, Azure Geo-Redundancy & WORM Immutability

    Deep cryptographic and distributed-storage breakdown of Managed Cloud Storage hosted via Microsoft Azure (/cloud-storage): client-side AES-256-GCM DEK/KEK envelope encryption, LRS/ZRS/GRS/RA-GRS failure domains, Hot/Cool/Archive FinOps tiering, SEC 17a-4 WORM locks, and HMAC-SHA256 SAS URLs.

  • Frequently Asked Questions
  • How does SAU Multi-Model Cloud Database prevent vendor lock-in while supporting five data models?
  • Why use HTTP ETag and If-Match headers instead of database row locks for AI agents?
  • How do SAU Cloud Identity, Key Vault KMS, and Cloud SIEM work together during a credential incident?
  • What workloads benefit most from AMD SEV-SNP Confidential Enclaves vs Serverless Functions?
  • Self-Serve Infrastructure

    Deploy Managed Cloud Storage & Multi-Model Cloud Databases

    Start with 5 GiB free Azure-hosted Cloud Blob Storage ($9/mo for 250 GiB ZRS, $29/mo for 1 TiB GRS with double AES-256-GCM + Azure SSE encryption & WORM locks) plus 100K RU/mo free Multi-Model Cloud DB.

    Explore Cloud Storage Browse All Cloud Services