Running Lorvara in-house

In short

• Run Lorvara inside your own estate when a subscription cannot meet a constraint you cannot move
• Your own generation endpoints: your model providers, your accounts, your contracts (How you’ll use it)
• Your own storage, so assets and records never leave your infrastructure
• The terms you have already negotiated with your providers still apply, because you are still the customer
• A scoped engagement, with the details on our website (Talk to Gravital Digital)
• Built and supported by Gravital Digital

Some organizations cannot send work to someone else’s infrastructure. A brand under NDA before a launch, a client whose contract forbids third-party storage, a team whose legal position on model providers is already settled and not negotiable. The hosted product is not the right answer for them, and pretending otherwise helps nobody.

A custom build is the same product with the boundaries moved.

How you’ll use it

Your generation endpoints. Point Lorvara at the model providers you already have relationships with, on your own accounts and your own commercial terms. The Prompt Agent, the Skills and the brief system work the same way; what changes is where the requests go.

Your storage. Generated assets and the records describing them live in your infrastructure rather than ours. Nothing has to leave your estate for the product to work.

Your fork. A custom build is a fork, so it can carry integrations, naming and behavior specific to your organization rather than waiting on a general release.

Everything else is the product you can already read about here. Briefs, Key Prompts, Skills, the shot list, the agent: the documentation in this site describes a custom build as accurately as it describes the hosted one.

For producers

This is a build, not a plan tier. It is not a checkbox on the pricing page and it does not come with a procurement cycle attached. It is a conversation about what your constraints actually are, followed by a build that meets them.

The hosted product stays the fast path. If your constraints allow it, a subscription gets you working this afternoon and a custom build does not. The reason to fork is a constraint you cannot move (data residency, an existing provider contract, a security review you have already passed elsewhere), not a preference.

Talk to Gravital Digital

Lorvara is built and maintained by Gravital Digital, who have been building AI image-generation systems since 2023. Lorvara has evolved from feedback on our Midjourney and Key Prompt Manager apps. We are intimately familiar with the landscape and developing for the MediaGen space.

A custom build is a scoped engagement. You can view more details on our website.

Talk to us about your requirements

Tell us what your constraints actually are: data residency, an existing provider contract, a security review you have already passed elsewhere. We will tell you honestly whether a custom build is the answer, or whether the hosted product already does what you need. Both answers are common.

Start the conversation →