Your data stays where you put it.
Hybridyn is built on a single architectural promise: data sovereignty by construction. Self-hosted single-tenant, local AI by default, telemetry off by default, Apache 2.0 forever. This page documents what that means in technical detail — the guarantees, the encryption, the AI guardrails, and the sub-processors (which is a short list: none).
What Hybridyn never does
Negative claims are stronger than positive ones because they're falsifiable. Here are six things we will never do — and the code-level mechanisms that enforce each.
We never see your data
F-Pulse is self-hosted single-tenant. Source data moves from the source system through your F-Pulse process to your destination over your network — never through Hybridyn infrastructure. We have no hosted version, no proxy, no telemetry pipe carrying customer data.
We never default to a cloud LLM
The AI Copilot defaults to Ollama running locally on qwen2.5:7b. Your schema, query history, and pipeline definitions never leave the host. Cloud providers (Anthropic, OpenAI, OpenRouter, Gemini, etc.) are explicit opt-in — operator brings their own key, knowing prompts leave the host.
We never bind to your LAN by default
F-Pulse binds to 127.0.0.1 — invisible to your LAN. No accidental port exposure to coworkers, hotel WiFi, or conference networks. LAN-visible binding requires explicit FPULSE_ALLOW_LAN=1 or --host 0.0.0.0.
We never enable telemetry by default
Telemetry is opt-in only. The default install collects nothing, phones home to nothing, and registers nothing. If you opt in, the schema is documented and the data goes only to Hybridyn — no third-party analytics, no ad networks, no resold telemetry.
We never silently change the license
F-Pulse is Apache 2.0 forever. We won't repeat the Elastic/MongoDB/Airbyte/Redis pattern of relicensing the OSS after adoption. Plus is a separately-licensed commercial extension that consumes F-Pulse's public APIs — never imported into the OSS repo (boundary rule 2 of edition-matrix.md).
We never put credentials in LLM context
Sanitization gateway strips PII, credentials, API keys, and connection strings before the model sees data. The model literally cannot exfiltrate what it never receives. Enforced at the runtime layer, not by the prompt — survives jailbreaks because the rule lives below the prompt.
Per-edition posture
OSS ships with always-on Fernet credential encryption and a full audit log. Plus adds Vault-backed AES-256 with rotation, sigstore-signed audit export, and Llama-Guard safety classification on every agent turn.
Guardrails enforced below the prompt
The AI Copilot is bounded by runtime-enforced rules, not prompt instructions. A model that decides to ignore the rules can't — the runtime intercepts every tool call.
Bounded agent loop
Hard caps: 6 iterations max per run, 300s wall-clock for local Ollama / 120s for cloud providers, per-user daily token wallet. Stop button cancels mid-flight.
Tool-tier RBAC
25 tools across 3 tiers: 21 READ (permissive), 4 SAFE_WRITE (standard RBAC + idempotency cache), 1 HIGH_IMPACT_WRITE (strict RBAC + mandatory confirmation card).
Dry-run by default
New HIGH_IMPACT_WRITE tools execute in dry-run for the first 3 successful runs before unlocking live mode — even if the user clicks 'live'. Three-success threshold before live writes.
Idempotency cache
Write tools key on (tool_name + args + tenant). Duplicate calls within the TTL replay the cached result instead of re-executing.
Sanitization gateway
PII, credentials, API keys, connection strings stripped before the LLM sees any data. Enforced at runtime, not via the prompt.
Who touches your data
Because Hybridyn is self-hosted, the sub-processor list is much shorter than a SaaS competitor's. Hybridyn itself is not on the list — we operate no infrastructure that handles customer data.
| Party | Role | Note |
|---|---|---|
| Hybridyn (your installation) | Process and store your data | On infrastructure you operate. |
| Source systems you connect | Read data from | Your choice. Hybridyn never sees the connection or the data flowing through it. |
| Destination systems you write to | Write data to | Your choice. Same — Hybridyn has no visibility. |
| Optional cloud LLM (only if opted in) | Process Copilot prompts | Operator-configured, BYO-key. Default is local Ollama — no cloud LLM is used unless you explicitly enable one. |
Hybridyn Technologies Pvt Ltd is NOT a sub-processor — we operate no infrastructure that handles customer data. Comparable SaaS ETL platforms typically list 8–15 sub-processors (cloud hosting, CDN, analytics, support tooling, etc.) because they run your data through their stack.
Where we are on the standards landscape
Honest about what's certified, what's roadmap, and what's not applicable to a self-hosted single-tenant product.
In place today
- • Apache 2.0 license (audit-friendly)
- • Self-hosted single-tenant architecture
- • Encryption at rest (Fernet OSS, Vault AES-256 Plus)
- • Audit log of every authenticated action
- • Sigstore-signed audit export (Plus)
- • Compliance posture document in repo (
docs/ai-ops-contract.md)
On the roadmap
- • SOC 2 Type II attestation (Plus, planned)
- • HIPAA BAA template (Plus, planned)
- • ISO 27001 alignment documentation
- • Data Processing Agreement (DPA) template
- • GDPR Article 32 technical-measures attestation
Not applicable
- • Cloud hosting certifications (we host nothing)
- • CDN data-residency claims (no CDN)
- • Vendor-supplied uptime SLA on the OSS (you operate it)
- • Third-party penetration test of "our infrastructure" (no infrastructure of ours touches your data)
For deployment-specific compliance (HIPAA, GDPR, SOC 2 within your environment), the controls live in your infrastructure since Hybridyn runs there. We provide the technical substrate (encryption, audit, RBAC, sanitization); your security team owns the operational controls.
Your data is wherever you put F-Pulse.
EU? Run F-Pulse on a Frankfurt VPS. India? Mumbai. US? Wherever you like. There is no Hybridyn-controlled region that processes your data, because there is no Hybridyn infrastructure that processes your data. Data residency is whatever you choose for the host you run F-Pulse on.
Found a vulnerability?
Please don't file a public GitHub issue. Email hello@hybridyn.com with a description, repro steps, and your contact. We acknowledge within 48 hours and publish a fix on a coordinated disclosure timeline. See security.md in the F-Pulse OSS repo for the full policy.
Per-feature OSS vs Plus boundary — the source of truth this page is derived from.
View on GitHub →"F-Pulse" and "Hybridyn" trademarks of Hybridyn Technologies Pvt Ltd.
Trademark policy →