ostravský lab_
CSEN

03 / Services

Deployment design and prototype

Choosing between your own hardware and the cloud is not only a question of price. It involves data, operations, capacity and who maintains the solution long term.

What technical setup do we need, and how do local, cloud and mixed options differ?

Write to the Lab See the example protocol

01 / About the service

What we do for you.

We start from the required quality, performance, data rules and available resources. The deployment options are compared on your brief, with the assumptions under which the recommended configuration holds.

The Lab has its own development capacity for applications, integrations and MCP connectors for Czech applications. By agreement, a prototype can follow the design and verify an agreed assumption or function.

When this fits

  • Data must not leave the company, or contractual and regulatory reasons require it.
  • You need to estimate operating requirements before committing to a purchase.
  • You have a validated task and need to connect it to your systems.
  • You want to verify a function with a prototype before starting development.

What we need from you

  • An overview of the systems the solution has to work with.
  • Requirements for data, access and security.
  • Expected performance, availability and number of users.
  • Who will run and maintain the solution.

02 / How it runs

How we work

Scope, price and deadline are confirmed before the work starts. The steps follow the size of the brief.

  1. 01

    Assessing the options

    We compare local, cloud and mixed options against your requirements and constraints.

  2. 02

    Designing the configuration

    We describe the recommended configuration, its assumptions and an estimate of capacity and operating needs.

  3. 03

    Cost assumptions

    When it is part of the brief, we add an indicative cost model with the inputs it is based on.

  4. 04

    A prototype by agreement

    The scope, the delivered output and the way it is verified are defined in advance in a separate agreement.

03 / Output

Possible output, as agreed

The exact output is agreed with the scope. We always state the conditions under which the findings hold.

  • A comparison of deployment options.
  • A recommended configuration and its assumptions.
  • An estimate of capacity and operating requirements.
  • An indicative cost model with the inputs it uses.
  • A list of questions the implementation has to resolve.

What this does not include

  • A prototype verifies an agreed assumption or function; it is not a production solution.
  • Integration, security, monitoring and follow-up support are defined separately.
  • The cost model follows the stated inputs and changes with prices and load.

04 / Practical questions

Common questions about this service.

Basic orientation for a first conversation. The details always depend on the specific brief.

Do you run the solution after deployment?

Operation, monitoring and support are not part of the design. Their scope is agreed separately according to the project.

What are MCP connectors?

An interface through which an application exposes its functions and data to an AI agent. The Lab develops them for Czech applications and uses them in integrations.

Can we start with a prototype?

We can, but we recommend testing the assumption it rests on first. Otherwise it gets tested during development.

05 / Services

Other services of the Lab.

The services build on each other. You can start with any of them, depending on where you are.

Write to the Lab

A new version is available.

An update is ready. Load the latest content, or keep reading this page for now.