Platform Architecture & Integration
PulseGate provides secure virtual desktop and browser workspaces delivered via high-performance regional session gateways. This document outlines routing topology, SDK integration, and zero-retention policies.
Regional Edge Routing Architecture
VDI sessions, display decoders, and package mirrors stream directly from regional Edge clusters (e.g. gw-<region>.pulsegate.cloud and portal-<region>.pulsegate.cloud), never the corporate apex domain. Replace <region> with your active regional cluster code (as published on our backbone directory).
Developer Toolchain Integration
1. Web Workspace Portal Client
Embed interactive workspaces in your corporate portal using the ES module client:
<!-- Regional workspace portal mirror (e.g. https://portal-<region>.pulsegate.cloud/portal/v1/client/) -->
<link rel="stylesheet" href="https://portal-<region>.pulsegate.cloud/portal/v1/client/theme.css">
<script type="module">
import { WorkspaceSession } from 'https://portal-<region>.pulsegate.cloud/portal/v1/client/client.js';
const session = new WorkspaceSession({
endpoint: 'https://gw-<region>.pulsegate.cloud',
canvas: document.getElementById('viewport'),
});
await session.connect('<TENANT_TOKEN>');
</script>
2. Hardware-Accelerated WASM Display Decoder
Decode streamed AV1 / H.264 desktop frames with low CPU overhead:
const decoder = await WebAssembly.instantiateStreaming(
fetch('https://portal-<region>.pulsegate.cloud/portal/v1/client/decoder-h264.wasm')
);
3. Client Manifest & Endpoint Discovery
Query client asset specifications and available codec engines:
fetch('https://gw-<region>.pulsegate.cloud/portal/v1/client/manifest.json')
.then(res => res.json())
.then(console.log);
Dedicated Tenant Access
PulseGate does not operate public self-service signups. Capacity is reserved exclusively for enterprise teams under dedicated hypervisor session broker pools, zero-trust network perimeter, and corporate identity federation with strict endpoint zero-data retention.