Bundles

The right starting configuration for how you work.

A bundle is not a pricing tier, a feature list, or a rigid package. It is a curated set of capabilities pre-configured for a specific use case — a coherent starting point. The organization customizes from there.

A bundle is a starting point, not a limit. An intelligent starting point, unlimited growth.

Clear the misconception first

What a bundle is — and the three things it is not.

The word does not behave the way it usually does. Before you pick one, it helps to know what a bundle on this platform actually means.

What people assumeWhat a bundle actually is
A pricing tier A box that fixes what you pay and locks what you get. A capability configuration. Pricing is handled separately during onboarding, based on your size, usage, and requirements.
A fixed feature list A checklist of features you are stuck inside. The capabilities most relevant to one organizational need, assembled correctly — intentional, not a random selection.
A rigid package A ceiling you outgrow and have to replace. A foundation. You start here and extend with additional capabilities as needs evolve. The bundle is the floor, never the ceiling.

How to find yours

You do not have to pick one before we talk.

  1. Start from how you work

    Read the bundle whose context sounds like yours. Each one is named for an organizational need, not a price point — the fit usually announces itself.

  2. Expect to sit between two

    Many organizations find their needs span more than one bundle, or combine elements from several. That is common, and it is exactly what the configuration is for.

  3. Let the conversation get specific

    The bundles are a starting framework, not a decision you owe us up front. We map your requirements and configure the right starting point from there.

The same ground under every bundle

Whichever you start from, it is the infrastructure these organizations already run on.

A bundle is not a separate product — it is a configuration of one ecosystem. The space, the data, and the access rules stay entirely yours.

  • Insel Spital · University of Bern

    Trusted in healthcare and academia

    Demanding knowledge environments operate on the same platform that carries your bundle.

  • RUAG · Credit Suisse

    Vetted at enterprise scale

    Your starting configuration sits on infrastructure already proven inside large, regulated organizations.

FAQ

Questions about bundles.

  • Is a bundle a pricing tier?

    No. A bundle is a capability configuration — a curated set of capabilities assembled for a specific use case. Pricing is handled separately during the onboarding process. The bundle defines what is included; pricing depends on your organization size, usage, and requirements.

  • Can we add capabilities beyond the bundle?

    Yes. Every bundle is a starting configuration, not a ceiling. Organizations regularly extend their bundle with additional capabilities as their space evolves. The bundle gives you a coherent foundation; growth happens from there.

  • What if our use case spans multiple bundles?

    That is common. Many organizations find their needs sit between two bundles or combine elements from several. The right approach is a strategy conversation: we map your specific requirements and configure the right starting point from there. Contact us to start that conversation.

  • Do we need to choose a bundle before talking to you?

    No. The bundles exist to give you a starting framework, not to force a decision before a conversation happens. Reach out anytime. We will help you identify the right configuration based on your organization and context.

Ready to explore your options?

Whether you know which bundle fits or you are still figuring it out, both paths lead to the right place.