What Managed Lore Hosting Changed for Indies - 2026

If you searched lore hosting after 1 October 2026, you do not need another “Epic killed Perforce” headline. You need a map of what actually opened: managed hosting for Epic’s open-source Lore version-control engine — signup, push, share a link — while Epic still ships the engine and leaves production readiness at pre-1.0.

Interlinked Files published Managed Lore hosting open to everyone from October 1, 2026. The authoritative Lore stack still lives in the EpicGames/lore README and the Lore roadmap. The same week Discord still treats “we’re on Lore now” as a depot migration command. It is not.

This page is the what-changed read. It is not the first indie spike evening (local demo server, throwaway commit, keep/hold receipt). It is not Stop Treating Managed Lore as Your Perforce Drop-In (overnight cutover refusal), and it is not a twelve-check migration kit. Those own lab rituals, refusal tables, and numbered gates. This URL owns the October 1 change map — what shipping managed hosting changed, what it did not, who it hits, and what to do Monday.

Why this matters now

Until October 1, most indie conversations about Lore stopped at “clone the MIT repo and run a server.” That was true. Epic open-sourced Lore as a next-generation VCS optimized for code plus large binaries, with a blunt README note: pre-1.0, interfaces and APIs may change. UEFN already uses Lore internally, but open-source clients still cannot open UEFN projects because of the Oodle versus Zstandard compression gap — Epic says that convergence is in progress on the roadmap.

What changed on October 1 is the hosting surface. Interlinked says it ran managed Lore as an alpha from 13 August 2026, then opened signup to anyone with a confirmed email: push a project, send a link, pay for bytes rather than seats. On that same morning their comparison table still listed Diversion on a waitlist, Anchorpoint as “more on that soon,” and Epic as no hosted service — run it yourself.

GitHub showed 9068 stargazers on EpicGames/lore by 29 October 2026 (API read in our evidence pass). The June Hacker News thread on Lore as open-source VCS still sits at 1276 points. Demand is not imaginary. Misreading “hosted Lore exists” as “replace Perforce this sprint” is.

Direct answer: Treat 1 October as a new hosting option, not a migration command. Separate self-host Epic Lore from Interlinked’s HTTPS vault. Read the UEFN incompatibility line out loud. Lab on a throwaway project before you touch the Steam ship depot. Keep Git LFS or Perforce as the ship-of-record until a written cutover plan exists.

Who this read is for

Time: 35–45 minutes to read. First hosted evening: spare machine or throwaway folder only.
Honest limit: Interlinked’s post, Epic’s README, and the Lore roadmap are authorities. Prices, waitlists, and star counts move — re-check the morning you adopt.

Non-repetition

The one-paragraph version

On 1 October 2026, Interlinked Files opened managed Lore hosting to everyone after an alpha that began 13 August. Lore remains Epic’s MIT open-source version-control engine for code and large binaries; Epic still does not sell Lore-as-a-service. Interlinked hosts a Lore vault over HTTPS (Cloudflare / R2), bills $5.99 per 100GB of storage or transfer (and per further 1,000 saves), with no per-seat charge, and a free tier for confirmed email. You push with Interlinked’s ifile CLI or desktop app — not Epic’s lore network protocol against their vault. Open-source Lore still cannot open UEFN islands (Oodle vs Zstandard). Epic still calls Lore pre-stable 0.x. Anchorpoint’s June 2026 self-hosted benchmark (UE 5.8, 63.5 GB) remains a measure of the engine, not Interlinked’s cloud path. Diversion and Anchorpoint were still waitlist / “coming soon” on that morning’s public table.

Highlight map (what Oct 1 put on the table)

What “managed Lore hosting” means in plain words

Lore is the version-control engine: CLI, server, formats, chunking, Merkle revisions. Epic publishes it under MIT and documents a local demo install in the README.

Managed hosting means someone else runs the durable vault — database, object storage, TLS edge, billing — and hands you an account. Interlinked’s product is that vault plus clients that speak their HTTPS protocol while keeping Lore’s on-disk project format.

Three sentences studios mash together wrongly:

1. “Lore is open source” → true (MIT).
2. “Someone hosts Lore for us now” → true for Interlinked as of Oct 1 (and possibly others later).
3. “So we can delete Perforce / Git LFS this week” → false until you have a written cutover, a UEFN answer if you need one, and a pre-1.0 risk owner.

If you only need the local spike, stay on the spike evening. This page assumes you heard “hosted” and need the October map.

Self-host vs managed — decision matrix

Beginner path: If nobody on the team wants to babysit a server, managed hosting is the interesting October change. If legal says files cannot leave the building, Oct 1 changed nothing for you — stay self-host or stay on current VCS.

Working-dev path: Document which protocol your automation uses. A script that shells Epic lore against localhost will not silently work against Interlinked. Treat clients as part of the cutover checklist.

The hosting landscape on the morning of October 1

Interlinked’s public table is useful as a snapshot, not as eternal truth. Re-check competitors before you sign a year of budget.

What Oct 1 changed for discourse: “There is nowhere to host Lore but your own servers” stopped being true for teams willing to use a third-party vault. What it did not change: Epic still does not operate that vault; the engine remains 0.x; UEFN still needs the compression convergence on Epic’s roadmap.

Pricing and company diligence (bytes, not seats)

Interlinked’s diligence-friendly claim is no per-seat charge. Their worked example for 20 people, 1 TB stored, 1 TB downloaded in a month quotes $113.81 on Interlinked versus higher seat-heavy Perforce cloud list math on the same page. Treat every vendor’s comparison table as marketing until your finance person re-runs it with your peak transfer month.

Free tier (confirmed email), as published Oct 1:

• Limited hosted projects
• 30GB storage
• 100GB transfer / month
• 1,000 saves / month
• Unlimited writers/readers within those caps
• SSO / SCIM called out as included even on free

Paid entry: $5.99 / month for unlimited projects with 100GB storage, 100GB transfer, 1,000 saves, then $5.99 per further 100GB of storage or transfer, or per further 1,000 saves.

Diligence checklist (print this)

1. Data residency / DPA — where do chunks live (they describe Cloudflare R2 / Workers)? Does your publisher contract allow that region set?
2. Exit — can you export a full Lore history you can re-host on Epic’s server later? Schedule an export drill in week one.
3. Auth — SSO/SCIM claims vs your Okta / Entra ticket queue.
4. Support SLA — indie free tier vs paid; who pages when a push fails during a crunch?
5. Pre-1.0 — write “Epic Lore is 0.x; Interlinked tracks Epic releases” into the risk register. Do not hide it from the board deck.
6. UEFN — if any title is a Fortnite island, managed OSS Lore does not solve sync today.
7. Cost model — model a bad month (cinematic dump, full clone storms), not only the happy 1 TB example.

Companies evaluating this for a 30-person Unreal team should compare seat math they already hate against egress math they might not have measured. Neither is free. Oct 1 mainly changes which invoice line item you argue about.

Push path — four commands and one trap

Interlinked documents a four-command start (npm/Bun global CLI):

npm install -g @interlinkedfiles/cli
ifile auth create
ifile auth verify
ifile push ./MyUnrealProject

ifile push prints a link. Teammates ifile clone <link> or open the link in a browser. Git vocabulary (commit, log, branch, clone) is intentionally familiar.

The trap: Interlinked states clearly — push with their clients, not Epic’s lore command against their vault. The vault speaks HTTPS through Cloudflare, not Lore’s native network protocol. The folder on disk stays Lore format either way. If a lead pastes the Epic quickstart into Slack and someone aims it at Interlinked credentials, you will burn an evening on a protocol mismatch that is documented, not mysterious.

Beginner evening (90 minutes, throwaway only)

1. Confirm email; stay on free tier.
2. Push a tiny folder (text + one medium PNG), not the entire UE 5.8 tree.
3. Clone on a second machine or second user.
4. Break something on purpose (edit binary, push again) and read the history UI.
5. Write three lines: protocol used (ifile), project size, whether you would trust this for ship next month (yes / no / only lab).
6. Do not disconnect the Git LFS remote on the Steam title.

Working-eng evening (half day)

1. Measure current Git LFS or Perforce pain: clone time, LFS pointer failures (help), seat invoice.
2. Push a representative Unreal or Unity project subset (engine plugins + content sample), not a toy.
3. Time first push, second push (dedup claim), and fresh clone.
4. Script auth for CI with a non-human account if SSO allows — or document that CI stays on Git until SSO lands.
5. File a one-page ADR: keep ship on current VCS; Lore hosting = lab; revisit after Epic roadmap items you care about (locking scale, Unreal Editor plugin).

What the Anchorpoint benchmark is — and is not

Interlinked leads with Anchorpoint’s June 2026 numbers on a self-hosted Lore 0.8.3 server: Unreal Engine 5.8, 392,559 files, 63.5 GB — first push 5m 16s for Lore vs 1h 6m Git LFS vs 1h 23m Perforce; stored size 22 GB Lore vs 57 GB Git vs 32 GB Perforce; fresh clone 20m 21s Lore vs slower Git LFS / Perforce on that run.

Use those numbers to understand why people care about the engine. Do not paste them into a board deck as “Interlinked is 12× faster than Perforce.” Interlinked themselves say the benchmark measured a self-hosted server, not their service, and Anchorpoint noted cloud object-storage setups need serious tuning. Your managed latency, packing, and cache behavior will differ.

Indie translation: if your pain is “first push of a giant Unreal tree melts the afternoon,” Lore’s chunking thesis is relevant. Proving it for your tree still requires your stopwatch on the path you will actually use (self-host or managed).

UEFN and the Oodle wall (unchanged, still critical)

Epic’s README and Interlinked’s fine print agree: UEFN islands cannot come across yet. UEFN’s Lore build compresses with Oodle; open-source Lore uses Zstandard. Until Epic finishes moving UEFN onto the open compression format (roadmap theme: Lore OSS and UEFN compatibility, 2026, in progress), open-source clients — including Interlinked’s — cannot open those projects.

If your studio’s loudest Lore request comes from a Fortnite Creative / UEFN pipeline, October 1 managed hosting does not unlock that workflow. Put the island on the spike backlog for after Epic’s compatibility work lands, and keep this URL’s Monday plan aimed at ordinary Unreal / Unity / big-file folders.

Pre-1.0 honesty — what the roadmap still says

The roadmap is directional, not a contract. Themes that still matter for indie cutovers:

Managed hosting does not accelerate Epic’s Unreal Editor plugin. It only removes “who runs the server” for teams that accept a third-party vault and a separate client. Studios that refuse any VCS without an in-editor plugin should treat Oct 1 as interesting infrastructure, not a green light.

What did not change on October 1

Write these on the whiteboard before the Discord announcement:

1. Epic still does not host Lore for you.
2. Lore is still pre-1.0 per Epic.
3. UEFN still blocked for OSS tooling.
4. Your Steam / console ship repo did not magically migrate.
5. Git LFS pointer bugs still exist on the old remotes (help).
6. Perforce seat invoices still arrive until you cancel them on purpose.
7. Benchmark glory is still mostly self-hosted Anchorpoint data.
8. Diversion / Anchorpoint managed may open later — do not assume Interlinked is the forever monopoly; do assume you need an exit drill either way.

Monday plans by role

Solo indie / beginner

Goal: Understand the noun “managed Lore hosting” without breaking ship.

1. Read Interlinked’s short version and Epic’s pre-1.0 note.
2. Optional: free-tier push of a throwaway folder.
3. Paste the Discord brief below into your studio channel.
4. Keep shipping on current VCS.

Tech art / build eng

Goal: Timed lab on a representative subset.

1. Pick Interlinked or self-host — document which.
2. Time push / re-push / clone.
3. Note client (ifile vs lore).
4. Open ADR: lab only until locking / editor plugin / UEFN needs are met.

Studio lead / producer

Goal: Kill the wrong rumor.

1. Say out loud: “Hosted Lore exists; Perforce cutover is a separate program.”
2. Assign owners for diligence checklist.
3. Forbid removing Perforce seats until exit + dual-run plan exists.
4. Calendar a revisit after Epic publishes tangible UEFN Zstandard progress or Unreal plugin betas.

Company / publisher diligence

Goal: Risk register, not blog hype.

1. Bytes vs seats model with a spike month.
2. Residency + DPA review.
3. Pre-1.0 + third-party host as two separate risks.
4. Require a restore-to-self-host rehearsal before any title depends on the vault for day-one content.

Failure modes you will hit if you skip the map

Creator Discord paste (copy as-is)

Oct 1: Interlinked opened managed Lore hosting (Epic’s open-source Lore engine). Bytes pricing, no seats, push via their ifile client — not a magic Perforce delete button. Lore is still pre-1.0. UEFN islands still don’t open on OSS Lore (Oodle vs Zstd). We’re labbing a throwaway project only; ship stays on [current VCS] until we have an ADR.

Pair with a community from 25 game-dev Discords (October refresh) — paste there, not into a fake on-site “community” URL.

How this pairs with the spike evening

Use both URLs without cannibalizing:

If you only have one evening, and you have never installed Lore at all, do the spike first. If leadership already bought the “hosted Lore” story from a LinkedIn post, start here so the rumor dies with a map.

Engine / launcher context (do not mash)

Opening Unreal or the Epic Games Launcher is a separate problem from hosting Lore:

• Launcher preview map: What Epic Games Launcher Preview Changed
• Step guide: Epic Games Launcher hub
• Engine ship-date bets: UE 5.8 lock playbook

Lore hosting does not replace launcher hygiene. Launcher hygiene does not give you a Lore vault.

Sample lab receipt (paste into Notion / git)

{
  "receipt": "lore_hosting_lab_v1",
  "date": "2026-10-29",
  "path": "interlinked_managed",
  "client": "ifile",
  "project": "throwaway_ue_subset",
  "first_push_minutes": null,
  "second_push_minutes": null,
  "clone_minutes": null,
  "uefn_required": false,
  "ship_vcs_untouched": true,
  "decision": "lab_only",
  "owners": {
    "eng": "",
    "producer": ""
  },
  "notes": "Oct 1 hosting map; Epic Lore still pre-1.0"
}

Fill the nulls with your stopwatch. If decision flips from lab_only without an ADR, you are doing rumor-driven ops.

Key takeaways

1. October 1, 2026 opened managed Lore hosting (Interlinked) to general signup — that is the news.
2. Epic still ships the engine, not a Lore cloud product.
3. Managed ≠ Perforce drop-in; write a cutover program or don’t cut over.
4. Push with Interlinked clients (ifile); do not assume Epic lore talks to their vault.
5. On-disk format stays Lore; transport and ops differ.
6. UEFN remains blocked for OSS / Interlinked until Epic finishes compression convergence.
7. Lore remains pre-1.0 — explore and pilot, don’t overnight-replace ship tools.
8. Anchorpoint’s fast UE 5.8 numbers measure self-hosted Lore, not your managed SLA.
9. Pricing is bytes and saves, not seats — model a bad transfer month.
10. Free tier is for labs; watch transfer and save caps.
11. Diversion / Anchorpoint may follow — keep an exit drill.
12. Keep the spike evening for local truth; use this URL for the hosting map.
13. Git LFS and Perforce pain still need their own fixes while you lab (LFS help).
14. Unreal Editor Lore plugin is still a 2027 roadmap item — artists are not “in-editor on managed Lore” by default.
15. Discord paste: hosted option yes; migration theater no.

FAQ

What is lore hosting after October 1 2026?

Lore hosting means running Epic’s Lore version-control engine as a durable remote for your projects. From 1 October 2026, Interlinked Files offers managed Lore hosting with public signup. Epic still expects most teams that want full control to run Lore themselves.

Did Epic launch a Lore cloud service?

No. Epic open-sources Lore and documents self-host / local demo paths. Third parties host managed vaults. Do not conflate “Epic made Lore” with “Epic hosts my depot.”

Is managed Lore a Perforce replacement?

Not automatically. Lore targets code-plus-large-binary workflows and can be faster on some benchmarks, but cutover needs locking maturity, client training, UEFN answers if relevant, pre-1.0 risk acceptance, and a dual-run plan. Treat Oct 1 as a hosting option, not a seat-cancellation event.

Can I use Epic’s lore CLI with Interlinked?

Interlinked says no for their vault: use ifile or their desktop app. Their vault speaks HTTPS through Cloudflare; Epic’s native Lore protocol is a different path. The project folder format remains Lore either way.

Can I host a UEFN island on managed Lore?

Not yet. Oodle (UEFN) vs Zstandard (OSS Lore) blocks open-source clients, including Interlinked. Watch Epic’s OSS/UEFN compatibility roadmap work.

Is Lore production-ready?

Epic marks Lore pre-1.0: formats aim to stay readable, but APIs and protocols can still change before 1.0. Interlinked ships their own Lore build and tracks Epic releases. For ship titles, keep a written risk owner.

How much does Interlinked Lore hosting cost?

As published Oct 1: free tier with confirmed email (limited projects, 30GB storage, 100GB transfer, 1,000 saves). Paid from $5.99/month with 100GB storage/transfer and 1,000 saves, then $5.99 per further 100GB or 1,000 saves — no per-seat charge. Re-read their pricing page before budgeting; numbers can change.

Should beginners start with managed hosting or the local spike?

If you have never touched Lore, do the local spike evening first so nouns stick. If leadership already assumes “we have Lore cloud now,” read this map first, then spike.

What should we tell Discord?

Use the paste block above: Oct 1 hosting is real; pre-1.0 and UEFN limits are real; ship VCS stays until an ADR says otherwise.

Where do I go for launcher or engine issues?

Launcher: guide hub and preview what-changed. Engine dates: UE 5.8 playbook. Those are not Lore hosting.

Sources (primary)

• Interlinked — Managed Lore hosting open to everyone from October 1, 2026
• EpicGames/lore README
• Lore roadmap
• Lore FAQ
• Lore quickstart

October 1 did not end Perforce. It ended the sentence “there is nowhere to host Lore but your own servers” for teams willing to trust a third-party vault. Use the map. Lab on purpose. Leave the ship depot alone until the ADR is boring.