Strom Enterprise

Strom, built into your company.

Everything the public API does, plus an engineer who builds your workflows, proof on your own cases before go-live, GPUs that run only your traffic and a contract under German law.

  • A German company, German law
  • A named engineer
  • No US-owned provider gets your requests

On your own

  • The docs
  • You test it
  • Shared GPUs
  • New versions for all
  • Prepaid balance
  • Email

With Enterprise

  • Your engineer
  • Proven on your cases
  • GPUs just for you
  • Your version, pinned
  • Your contract
  • A shared channel

An engineer builds it with you.

On the public API, you build from the docs. Here a named engineer maps your process, writes the questions and wires the workflows.

  1. 1Map your process

    Step by step, with the people who do it.

  2. 2Find the decisions

    Wherever someone reads something and picks an answer.

  3. 3Run it end to end

    Each decision becomes a question with your options, chained with your rules.

Included
  • A named engineer
  • A shared Slack or Teams channel
  • Onboarding for your team

Proven on your data before go-live.

On your own, you test it yourself. Here we run Strom on your cases at your threshold and hand you the result.

What you see before go-live
  • At your threshold, how many cases Strom decides alone and how often those are wrong
  • Every case it got wrong
  • Which decisions to leave with people

In production

Feddersen started with one workflow. Now Strom is spreading through the group.

With its software partner torwell, the Feddersen Group put Strom into its inventory app. A photo of a type plate fills in the record.

20,000
inventory items captured
325 h
of capture time saved
97.5%
less time per item
≈€15k
saved in the first workflow
Read the case study

Inventory was pure manual labour, and we tried several tools to cut it down. None of them worked, OCR included. Strom is the first that did. That gave us back countless hours in the first workflow alone and saved us not just money but a lot of frustration. That success is why we’re now expanding Strom to other areas of the group together with Uprelic.

Joachim Friedrich Head of Digital Office, Feddersen Group
Carved out together
  1. Live Inventory capture from photos
  2. Next Invoice processing
  3. Planned Other areas of the group

Capacity and a model that stay yours.

The public API is shared and moves with everyone. Yours doesn’t.

  • GPUs that run only your traffic

    Public API
    Shared GPUs. Up to 512 questions in progress per account, and 429 when Strom is busy with everyone’s requests.
    Enterprise
    Reserved for you and sized with you to your volume.
  • A model that stays put

    Public API
    strom-fast moves to each new version.
    Enterprise
    Your version stays until you switch. We test each new one on your cases first.

Your contract, your assurances.

One contract with Uprelic GmbH under German law, instead of a prepaid account. Only European providers receive your requests.

  • One monthly invoice

    For the capacity you reserve, not a prepaid balance.

  • Retention you agree

    365 days, or the period in your contract. Zero data retention included.

  • Agent guard by contract

    Sessions set in your contract, not a plan limit.

  • Your own hardware

    Strom on premises, by arrangement.

Who receives your requests
  • OVHcloud Gravelines, France Runs our servers and the model Yes
  • Scaleway Amsterdam, Netherlands Stores our backups Encrypted, without the key
  • Cortecs Vienna, Austria Improves document extraction Only if you turn it on
  • AWS, Stripe, Google US-owned Sign-in emails, payments, Google sign-in Never
A German contract
Uprelic GmbH, German law, a DPA and answers to your security questionnaire.
Never used for training
Not now, not later, not even anonymised.
Our own model
Strom runs on our servers, not on another AI provider’s.

You stay in control.

Strom’s probabilities are calibrated, so the threshold you set decides how often it’s wrong. Before go-live, we measure on your cases how often it’s right at each threshold. Below yours, a person decides.

One workflow run
Duplicate?no 0.97continue
Matches the order?yes 0.91continue
Payment risk?medium 0.62ask a person

Held for a person, one answer was below 0.90

See why
Every answer with its probability and what happened next.
Move the line
Raise the threshold, and more goes to a person.
Look back
Every run kept as long as agreed, or only on your side.

What purchasing asks us.

Which decisions is Strom not for?

Decisions that need arithmetic, several steps of reasoning or facts that aren’t in the input. And the high-risk uses our acceptable use policy excludes, such as hiring and managing staff, credit scoring, pricing life or health insurance, and education. We tell you in the first call if a decision doesn’t fit.

What about the EU AI Act?

You are the deployer of what you build with Strom. The high-risk uses of Annex III are excluded by our acceptable use policy. Every request is stored with its answers and their probabilities for your plan’s retention period, or the period in your contract. With zero data retention, you keep that trail on your side.

Is there an SLA?

Not on the public API during the beta. Our terms commit to no level of availability, response time or throughput there. When we set up a dedicated deployment for you, we agree these in your contract.

Can you fill in our security questionnaire?

Yes. Send it with your enquiry or after the first call. We don’t hold an ISO 27001 certification or a SOC 2 report yet. Our data processing agreement says what we provide instead, and it is public, like the list of subprocessors.

How is a dedicated deployment priced?

By the capacity you reserve, in a contract with a monthly invoice. We size it with you from your volume, your latency needs and whether images are involved.

Can we run Strom on our own servers?

Yes, by arrangement. Tell us about your setup and your requirements, and we’ll work out the details with you.

Can we start on the public API and move later?

Yes. Dedicated uses the same API and request format, so moving is a change of address and key.

What happens if Uprelic changes course?

You can export your data at any time, free of charge. The API takes the same request format as TypeSafe’s Jev, so moving is a configuration change, not a rewrite. And your contract fixes how far in advance we would announce an end of service.

Tell us about your workflow.

A person from our team replies within one business day.

Prefer to write? sales@uprelic.com