🧭 Founder Direction · V1 · September 2026
This page explains why REMAP's technology stack is what it is — the default, the reasoning, and
when to depart from it. Current direction; for the operational infrastructure SOPs, see the links
below.
REMAP's default is n8n automations running inside the Private AI platform — not because of the
specific tools, but because building in infrastructure REMAP controls is what makes speed-to-value
possible. The compliance grade flexes to the client's regulatory reality, never to their size or
budget.
The default:
The reasoning is speed-to-value, and it comes down to control:
💡 Deploying inside infrastructure REMAP already controls — rather than waiting on a client's
own IT department, credentials, and back-and-forth — is exactly what lets REMAP move fast.
Open-source tooling needs a home REMAP governs; Private AI is that home. The moment work depends on a
client's internal IT to provision access, speed collapses into a queue. Building in REMAP's own
environment removes that friction entirely — which is the whole point.
How much compliance architecture a client gets is driven entirely by their regulatory reality or
business type — never by budget or company size. The real test is one question:
💡 "Is this a business-ending compliance risk for them, or a genuine IP concern?"
The four grades, from lightest to strongest:
| Grade | What it is | Triggered by |
|---|---|---|
| Default | LiteLLM with standard third-party platforms; no extra logging or residency controls | No special compliance need |
| Standard | Same LiteLLM-managed routing as Sovereign, without the aggressive zero-data-retention logging | A lighter-touch step up |
| Sovereign | Zero-data-retention agreements to still use third-party frontier-model inference, routed through LiteLLM in an open-source-tooled container | A regulatory or data-residency requirement tied to the client's jurisdiction/industry |
| Enclosed (highest) | A fully private AI instance inside REMAP's own AWS — infrastructure and model contained, nothing leaking to any third party; only open-source tooling in a secure container (e.g. Open WebUI instead of any third-party interface) | A hard regulatory requirement, an IP-protection need, or a genuine data-sovereignty/perception concern |
💡 Honest note: the practical difference between Default, Standard, and Sovereign is more about
intensity of practice than architecture — they share the same LiteLLM routing. Enclosed is the
genuinely different one. What decides the grade is the client's compliance reality, full stop.
The default (REMAP's own AWS/Private AI) is used unless there's a genuine client requirement to
do otherwise — for example, a client needing to stay inside their own Azure tenant for
data-residency or compliance reasons.
When that happens:
Absent a genuine client requirement, REMAP defaults to its own environment because it minimises
friction — with the option to migrate the client out later if they ask.
💡 The rule: depart from the default only for a real client requirement, not a preference — and
when you do, agree the autonomy and the cost ceiling upfront so speed isn't lost to permission-
seeking.
🟢 confirmed · 🟡 draft/in-progress · ⚪ illustrative
This page is the why. For the how:
Part of the REMAP Founder Vision space · V1 · Last updated September 2026