
Helioform Retires v2 Embeddings on 2027-02-15; 11 Open-Source Connectors Still Default to v2
Helioform’s deprecation schedule sets a hard shutoff for v2-embed (1,536-dim) with incompatible v3 vector spaces, leaving 11 widely used connectors exposed.
§1 What Changed
FACT · CLAIM-GROUNDEDHelioform’s deprecation register posted a hard shutdown date of 2027-02-15 for its v2-embed endpoint, returning HTTP 410 errors after 00:00 UTC.C1
Helioform’s migration guide confirms v3-embed produces non-comparable vector spaces, requiring full corpus re-indexing rather than an in-place endpoint swap.C2
An audit of release notes and default config files across 11 open-source retrieval connectors shows all 11 still hardcode v2-embed as their default embedding model as of 2026-11-19.C3
SignalPost Analysis — Labelled inference, not reported fact (validated fact-sterile against claim ledger)
§2 Why It Matters
ANALYSISModel retirements with incompatible vector spaces are different from routine SDK bumps: every team that embedded customer documents over the last two years must re-embed, backfill, and cut over live search without breaking retrieval quality. Because 11 open-source connectors still default to v2-embed, downstream teams will discover the break late and pay for turnkey migration tooling.
Migration Paths Before 2027-02-15 v2-embed Shutoff
DECISION MATRIXFastest safe path if Helioform SDK stays embedded across services.
Strongest choice if you are paying the full re-indexing cost anyway.
- Cost Delta
- Re-embed once; own vectors permanently[analysis]
- Migration Effort
- Higher upfront hosting + eval setup[analysis]
- Lock-In Risk
- Eliminated — no forced vendor EOLs[analysis]
- Window / Timing
- Viable inside 90-day window[analysis]
§3 Second-Order Implications
A focused dual-write re-indexing CLI or managed backfill service targeting Helioform v2-embed to v3-embed has a hard 2027-02-15 forcing function and clear search intent.
Teams forced to re-embed their entire archive anyway have zero switching-cost advantage staying on Helioform, opening a window for self-hosted open-weight embedding models.
Maintainers of the 11 open-source connectors face urgent PR churn; sponsors who contribute clean v3 migration guides earn immediate developer mindshare.
▲ Better Positioned
- Migration and zero-downtime vector re-indexing toolmakers
- Open-weight embedding providers pitching "re-embed once, own your vectors"
▼ More Exposed
- Production RAG apps built on the 11 unpatched open-source connectors
- Teams without stored raw source chunks needed for re-embedding
§4 Decision Hooks
Operational options, not financial advice§5 Counter-Case (How This Read Could Be Wrong)
Enterprise pressure routinely pushes API providers to grant paid legacy extensions. If Helioform announces an extended paid v2 tier before January, urgency for third-party migration utilities would drop sharply.
Zero-Downtime Vector Migration Playbook
Anchored to 2027-02-15 (HTTP 410 shutoff date)C1
Quick Answers
Fact vs Analysis explicitly taggedCan existing Helioform v2-embed vectors be queried alongside v3-embed?FACT
No — Helioform’s migration guide confirms v3-embed produces non-comparable vector spaces, requiring full corpus re-indexing.C2
What happens to v2-embed calls after 2027-02-15?FACT
The v2-embed endpoint reaches hard end-of-life on 2027-02-15 at 00:00 UTC and will return HTTP 410 errors.C1
§6 What to Watch / Invalidation Triggers
FORWARD · FALSIFIABLE| Kind | Observable | Source | Threshold | Check By | Status |
|---|---|---|---|---|---|
| ✓ confirms | Helioform reaffirms the 2027-02-15 v2-embed shutoff with no legacy extension at T-30 | Helioform Deprecations | T-30 shutoff notice | 2027-01-20 | armed |
| ✗ invalidates | Helioform extends v2-embed EOL past 2027-02-15 or introduces a paid legacy compatibility tier | Helioform Deprecations | EOL extended | 2027-02-15 | armed |
§7 Evidence Ledger
LEDGER3 claims · 2 sources (2 primary) · 0 corroborated · 0 disagreements· verified 2026-11-19 18:05Z
Panel A — Claims (3)
Helioform will shut down the v2-embed endpoint on 2027-02-15, returning HTTP 410 after 00:00 UTC.
Show primary passage (Helioform API Deprecations · v1)
Deprecation Notice: v2-embed reaches end-of-life on 2027-02-15 at 00:00 UTC and will return HTTP 410.
Segment: si_00cbb552a8d6b9abfad3:1:p1 · Source: Helioform API Deprecations
Helioform’s v3-embed produces incompatible vector spaces requiring full corpus re-indexing.
Show primary passage (Helioform API Deprecations · v1)
Migration Guide: v2-embed and v3-embed vectors are not comparable; full corpus re-indexing is required.
Segment: si_00cbb552a8d6b9abfad3:1:p2 · Source: Helioform API Deprecations
Eleven open-source retrieval connectors still default to v2-embed as of 2026-11-19.
Show primary passage (BasaltDB & Gabbro OSS Governance · v1)
Connector audit snapshot (2026-11-19): 11 active open-source retrieval connectors configure model="v2-embed" by default.
Segment: si_d6ab168a58b0c3c8cfc5:1:p3 · Source: BasaltDB & Gabbro OSS Governance
Panel B — Sources (2)
Doc: Helioform Deprecation Register: v2-embed EOL
Doc: OSS Connector Default Audit (11 Repos)
Part of Convergence Thread
Open Radar →Forced Migration Windows: Deprecations & Source-Available Splits
Revision Trail (1 immutable version)
- v1 · auto · initial v2 signal assay · 2026-11-19T18:05:00Z