On-Premises AI Server

    Hippo Server puts Hippo Chat, Hippo API, and whatever else you need on a server in your building. Your data never leaves your network — not to a cloud provider, not to a model vendor, not to anyone. Full control. Full compliance. Full peace of mind.

    On-premises server

    What's the problem?

    Do you know where your data goes when you use AI?

    Every prompt you send to a cloud AI crosses a network boundary. Your confidential documents, customer records, internal strategy — it all passes through infrastructure you don't own, operated by companies in jurisdictions you can't control.

    For regulated industries, that's a liability. For everyone else, it's a question your legal team will eventually ask. And once data has left your network, there's no taking it back.

    Hippo Server keeps everything in-house. The model runs in your building, on your hardware, under your policies. You always know exactly where your data is — because it never went anywhere.

    How does it work?

    Four steps to your own AI server.

    From discovery workshop to a running system in four weeks.

    01

    Workshop: understanding your needs

    We sit down with your team and map out what you need — which products, which models, which integrations. You walk away with a clear spec and a realistic picture of what the hardware needs to handle.

    02

    We configure the right setup for you

    Based on your workload, we select which Open Hippo products go on the server — Hippo Chat, Hippo API, or anything else you need. We pick the models and make sure everything fits your use case and hardware budget.

    03

    We set everything up

    Hardware procurement, OS setup, software deployment, networking. We handle the full stack. Four weeks from signed contract to a running system on your premises.

    04

    Integration and onboarding workshops

    We connect the server to your existing systems and run hands-on workshops so your team can operate, manage, and extend it independently from day one.

    What do you get?

    Measurable results, not promises.

    Concrete outcomes your team can track from week one.

    Your data never leaves your building
    Full GDPR compliance by design
    No third-party access — ever
    Works offline and air-gapped
    Four weeks to a running system
    Your team owns and operates the stack

    Does it work in practice?

    Hippo Server in production

    "The sandbox let us prototype with real patient data from day one — something we could never do with a cloud service."

    Got questions?

    Common questions about Hippo Server.

    Straight answers on hardware, setup, and what to expect.

    How long does the setup take?

    Four weeks from signed contract to production. Week one is the discovery workshop and hardware spec. Week two covers procurement and infrastructure setup. Week three is software deployment and configuration. Week four is integration, testing, and handover with onboarding workshops for your team.

    What does it cost?

    Hardware starts at €40,000 for a dual Blackwell RTX 6000 Max configuration — the right choice for production workloads running multiple models and products in parallel. If you want to start smaller, we offer a DGX Spark entry package including the setup workshop for €8,000. That's a practical way to validate the approach before committing to full production hardware.

    What's the difference between the DGX Spark package and the full setup?

    The DGX Spark package is designed for piloting — you get real hardware, real software, and a real workshop, but at a fraction of the cost. It's ideal for teams that want to prove the business case internally before going to production. The dual Blackwell RTX 6000 Max setup is for production workloads where throughput, reliability, and uptime matter.

    Which software runs on the server?

    Whatever you need. Hippo Chat gives your team a private, self-hosted AI assistant. Hippo API gives your developers an OpenAI-compatible endpoint they can call from any application. We can add other models and tools on top depending on your use case — the workshop in step one is where we figure that out together.

    Does it work without internet access?

    Yes. Hippo Server is fully self-contained — no cloud calls, no telemetry, no external dependencies at runtime. This makes it suitable for air-gapped environments, regulated industries, and any setting where outbound data transfer is not acceptable.

    Can we add more software later?

    Yes. The server is built to be extended. If your needs grow — new models, new tools, new integrations — we can add them without replacing the hardware or starting over. We stay available for support and expansions after the initial handover.

    Let's look at your setup.

    30 minutes, no pitch deck. We'll map your current AI usage and show you exactly what a Hippo Server would look like for your team.