Skip to content
maskera

Run it in your environment

Gateway runs the masking on your own servers

Gateway runs as an internal HTTP API between your application and the AI services you approve. Personal data detected by Gateway is replaced before traffic leaves your network.

Your message will be emailed to hej@maskera.dev.

One container, no GPU or database

The signed, version-pinned container includes both the software and the Swedish model. You do not need a separate model server.

Packaging
One signed container for Docker Compose or Kubernetes with Helm.
Model
The 43 MB Swedish model is built in and is not downloaded during operation.
Hardware
Runs on CPU. Start with 2 CPU cores, 2 GB RAM and about 1 GB of disk per instance.
Scaling
Gateway is stateless and can run as multiple instances without a shared database.

Want to understand the entire flow before buying?

The technical walkthrough explains the difference between the customer portal and the container, the integration options, the identity boundary and what is included.

How Gateway works technically

How text flows

  1. Your application

    Sends the original text to Gateway instead of directly to the AI service.

  2. Maskera Gateway

    Applies your shared rules and replaces detected personal data in memory.

  3. Your AI provider

    Receives the text after masking, through your own key and your list of approved services.

Every AI request routed through Gateway is masked before it reaches the AI service you approved. Maskera's servers are not part of the flow, and the license is verified locally.

From order to renewal

  1. Order and activate

    After ordering, the agreed pilot or annual license is activated and becomes available to the organization's owner.

  2. Download the package

    You receive a signed, version-pinned delivery with a license and baseline configuration for your environment. Runtime secrets stay with you.

  3. Start it in your environment

    Run two commands on a Linux server, or install with Helm on Kubernetes. Gateway needs no database.

  4. Renew without interruption

    When the agreement renews, you receive an updated license in the customer portal and replace it according to the delivery instructions.

docker compose up -d   # starts Gateway from the package
sh ./smoke-test.sh     # makes a real masking request with your key

This starts Gateway on a Linux server. For Kubernetes, use two secrets and a Helm installation with values from the same package.

What is included

  • Version-pinned container and Helm package
  • License for the agreed test and production environments
  • Secure baseline configuration with the key stored only as a hash
  • OpenAPI specification and automated functional test
  • Signed releases, software bill of materials (SBOM) and security updates
  • Weekday email support

What you need

  • Docker Compose or Kubernetes with Helm
  • At least 2 CPU cores and 2 GB memory per instance as a normal starting point
  • Outbound HTTPS to the AI service you choose, if the proxy is used
  • Your own TLS proxy or load balancer in front of Gateway
  • Someone who can manage networks, secrets and updates in your environment

Built to be reviewed

Gateway retains nothing between requests. Text, the restoration key and AI responses are processed in memory and are not written to a database or log. The signed container is pinned to an exact version and comes with a software bill of materials (SBOM). You control the network, identity and log retention around the service.

Clear division of responsibility

Maskera is responsible for

  • The Gateway software and Swedish model
  • Signed releases and security updates
  • License delivery, documentation and agreed support

You are responsible for

  • Servers, Kubernetes, networking, TLS and configuration backups
  • Your AI keys and relationship with your chosen AI provider
  • Testing your text types and human review when a miss could have consequences

Frequently asked questions

Do we have to speak to sales?

Gateway is available as a 60-day pilot or annual license. You begin with a technical walkthrough. Custom service-level agreements or installation engagements are handled separately.

Is the masking perfect?

No. No automated solution finds everything. Test your own text types and have a person review results when a miss could have serious consequences.

Can we use our company sign-in?

Yes. Gateway can connect to your company identity through OIDC and assign roles. The standard package starts with a local API key so you can verify the installation immediately.

One production environment and one test environment, signed releases, security updates and weekday email support.

Register interest

Your message will be emailed to hej@maskera.dev.