RunLocalTools

The Enterprise Deployment & Self-Hosted Portal

For teams that can’t use public tool sites. Run the toolkit inside your own environment.

RunLocalTools is designed around local processing, but some organizations have a different requirement:

The tools cannot be accessed from the public internet at all.

Banks, healthcare organizations, government contractors, regulated businesses and security-conscious teams may require software to operate inside infrastructure they control.

For those situations, we can discuss private deployment options.

Private deployment

The RunLocalTools toolkit is built and maintained in-house, which makes private deployment possible when the requirements are appropriate.

Depending on the environment, deployment may involve:

Internal web deployment

Run the toolkit from infrastructure controlled by your organization.

For example:

tools.yourcompany.internal

The resulting application can be made available to users through your organization’s own internal network.

Containerized deployment

Where appropriate, the application can be packaged for deployment through a container-based environment such as Docker.

This can make it easier for an organization’s IT team to manage the application within its existing infrastructure.

Offline or restricted environments

For environments with especially strict network requirements, the deployment architecture can be discussed around the organization’s connectivity and security constraints.

The exact approach depends on the environment rather than being a single one-size-fits-all package.

Why self-host RunLocalTools?

The public platform already follows a local-first architecture.

A private deployment can take that principle further by putting the application itself inside your organization’s controlled environment.

This can be useful when:

  • External web applications are blocked by policy.

  • Files cannot be processed through public services.

  • Internal users need browser-based tools without sending work to external processing platforms.

  • IT teams need control over where the application is hosted.

  • The organization operates in a restricted or disconnected environment.

For a technical explanation of the public architecture, see How Our Tools Work.

What is available today?

RunLocalTools does not currently operate a self-service enterprise store with a fixed deployment package and public price list.

Private deployment is handled as a technical project.

That means we first need to understand your environment before determining what can be deployed and how it should be packaged.

Useful information includes:

  • Approximate number of users

  • Operating systems

  • Browser requirements

  • Internal network architecture

  • Internet restrictions

  • Whether the environment is air-gapped

  • Deployment or container requirements

  • Which tools are required

Talk to us

If your organization needs a private or self-hosted deployment, use the form below and describe the environment as specifically as possible.

We’d rather evaluate the actual requirements than sell you a generic enterprise package that doesn’t fit.

For ordinary individual and commercial use, the public RunLocalTools toolkit remains available without an account or subscription.