ForgeLore

Plans for Unreal teams using large assets

Start with a hosted project, lock binary assets before editing, keep the team in sync, and add AI assistants safely when you are ready.

Free

Start with one hosted Unreal repository, asset locks, and scoped AI assistant access. No credit card required.

$0/ month

No credit card required

1 repositories1 seats10 GB-month storage20 GB transfer100 assistant credits
One hosted native Lore repository
One seat for a solo Unreal project
10 GB storage and 20 GB bandwidth included
100 assistant actions
No credit card required

Starter

A disciplined first production lane for small teams validating native Lore hosting.

$49/ month
3 repositories3 seats50 GB-month storage100 GB transfer500 assistant credits
500 agent actions
100 bandwidths
3 repositories
3 seats
50 storages

Studio

The default operating tier for asset-heavy teams shipping with sparse workspaces and shared locks.

$199/ month
10 repositories15 seats500 GB-month storage1,000 GB transfer5,000 assistant credits
5,000 agent actions
1,000 bandwidths
10 repositories
15 seats
500 storages

Enterprise

Custom native Lore edge, procurement, and governance limits for larger game productions.

Custom
Custom repositoriesCustom seatsCustom GB-month storageCustom GB transferCustom assistant credits
Unlimited agent actions
Unlimited bandwidths
Unlimited repositories
Unlimited seats
Unlimited storages

Flexible usage, controlled by your billing admin

Team and Scale share transparent marginal rates: $12 per extra seat, $15 per extra active repository, graduated storage from $0.12/GB-month, graduated transfer from $0.10/GB, and assistant credits from $10 per 1,000. Larger included allowances—not hidden unit discounts—differentiate Scale.

Overage is off by default. Admins can set per-feature spend limits, daily or monthly caps, warning thresholds, and optional automatic assistant-credit top-ups.

Billing, limits, and workflow

What does ForgeLore give my Unreal team?

A hosted Lore repository for large assets, a dashboard for locks and activity, team access controls, usage visibility, and safe assistant access for coding agents.

Can artists and engineers use the same project?

Yes. Engineers can work with code and branches while artists lock binary assets before editing. Everyone can see project status and active locks before work collides.

Can AI assistants work safely with the project?

Assistants can be given scoped access to read project status, recent activity, and locks. Broad content changes still go through the normal project workflow.

What happens when a plan limit is reached?

Free stays hard-capped. Team and Scale stay capped until a billing admin explicitly enables overage for that feature and sets spend, usage, and warning thresholds.