Tenant isolation
PlannedEvery institution is isolated at the runtime boundary. Content, attempts, and exports never cross tenants.
Security & reliability
Security and reliability are designed into the architecture.
QFlowLearn separates tenants, signs launches, freezes published content versions, and records attempt events so institutions can verify what happened before, during, and after an assessment.
Pillars
Eight things technical evaluators ask about.
Signed launch & bootstrap
PlannedLaunch tokens are signed and short-lived. Bootstrap is verified at the edge before any package payload is fetched.
Immutable content versions
ReadyOnce a version is published, it cannot be mutated. Corrections are new versions; learner attempts are anchored to the version they took.
Attempt event ledger
PlannedEvery meaningful attempt event is appended to a ledger that survives the runtime: start, item view, response, navigation, accommodation, and submit.
Operational audit
PlannedOperations on the runtime (re-scoring, version overlay, evidence export) emit auditable records.
Recovery plan
In build for launchLocal journaling, durable submit, and reconcilable attempts make recovery part of the architecture instead of a manual support process.
Cloudflare platform services
ReadyWorkers, Durable Objects, Queues, R2, and the global edge each have a defined role in launch, delivery, submission, evidence, or export.
Data retention & redaction
In build for launchRetention windows and redaction rules are explicit, documented per artifact class, and enforceable on request.
Hostnames & boundaries
Public hostnames are deliberate, not incidental.
Marketing, authoring, and delivery live on separate hosts so authentication, asset policy, and CORS surfaces are explicit. Internal codenames stay internal.
qflowlearn.com
Marketing, RFP pages, and evidence library. Astro on Cloudflare Workers.
app.qflowlearn.com
QFlowLearn authoring application. Host-only auth, explicit CORS allowlist.
take.qflowlearn.com
Learner delivery runtime. Token-based launch, no shared marketing cookies.
Security reviewers: ask for the architecture summary.
We will send the architecture summary, runtime contract excerpt, retention/redaction rules, and the launch artifact list, scoped to your security questionnaire.