Contact

Servers · Cloud · Security · Operations

Less worry about infrastructure. More room for your business.

We design, modernise and run infrastructure in your environment, in the cloud or on our platform. We cut costs where it pays off. Environments are brought into IaC, so they stay yours and do not depend on us.

Request a consultation

Our founders bring 10+ years of running infrastructure for banking and critical systems.

What we help with

Typical situations

The most common starting points in small and mid-sized companies. Each one shows the approach and its outputs.

A different situation: describe your environment →

Whether NIS2 applies to you is covered in the NIS2 guide →

Approach

No in-house operations team

  1. Environment inventory

    Systems, access, backups and operating procedures, including what external suppliers and internal staff know.

    Output: an overview of systems, access and backups

  2. Documentation and IaC

    We capture the environment in IaC and add documentation and runbooks for routine situations. Working parts are not changed without a reason.

    Output: the environment in IaC, with runbooks

  3. Operations takeover

    Monitoring, updates, backups and incident handling in your environment or on our platform, with agreed response times.

    Output: operations with agreed response times

Approach

Operations depend on one person

  1. Knowledge capture

    Systems, access, backups and operating procedures, mapped together with your administrator.

    Output: an inventory of systems and access that you own

  2. Documentation and IaC

    Documentation, IaC and runbooks that another administrator can work from. Working parts are not changed without a reason.

    Output: a documented environment that does not depend on one person

  3. Cover

    We agree on responsibilities for monitoring, updates and on-call. Your administrator stays the lead, or we take over operations entirely.

    Output: cover during holidays and sick leave

Approach

Outdated environment, risky changes

  1. Risk assessment

    System age, end of support, security findings and operational risks, ranked by impact and urgency.

    Output: a list of risks ranked by impact

  2. Incremental modernisation

    Changes in small steps, riskiest parts first. Every step is verified and has a rollback procedure.

    Output: an up-to-date environment in IaC

  3. Handover or operations

    We hand the environment over to your team with documentation, or take over its operations in your environment or on our platform.

    Output: an environment with ongoing maintenance

Approach

Rising infrastructure costs

  1. Cost analysis

    Cloud, servers, licences and manual operations work in one overview.

    Output: a cost overview by service and team

  2. Optimisation

    From switching off unused resources to architecture changes. Each measure has its saving and cost quantified up front. Sometimes the best option is to change nothing.

    Output: lower operating costs

  3. Ongoing control

    Budgets, alerts on unusual growth and a regular report.

    Output: costs under ongoing control

Approach

Preparing for NIS2 or ISO 27001

  1. Scope and gap assessment

    Whether and how NIS2 applies to you, and how the current state meets the requirements: access, backups, logging and procedures.

    NIS2 guide →

    Output: a scope assessment and a list of gaps

  2. Implementing controls

    By risk priority. Controls verified in operation, and the evidence auditors require.

    Output: controls in place and audit evidence

  3. Ongoing management

    One-off or ongoing: access, patches, backups and evidence are kept up to date.

    Output: evidence ready for an audit

Approach

AI use without rules

  1. Mapping AI use

    Tools in use, data flows and management of API keys.

    Output: an overview of AI use and data flows

  2. Shared rules

    A company chat with company sign-in, one gateway to models (LLM gateway) with limits, and rules for data processing.

    Output: AI behind company sign-in, with rules for data

  3. Visibility and operations

    Usage, costs and the results of automations in Langfuse. We run the platform in your environment or on our infrastructure.

    Output: a view of costs and results

Approach

New product

  1. Requirements

    Features, expected load, availability requirements and budget. No lengthy specifications.

    Output: a brief and a cost estimate

  2. Design and build

    An environment in IaC with backups and monitoring from day one. Hosting is chosen by cost and your team’s capabilities.

    Output: a documented environment ready for operations

  3. Launch and operations

    Go-live with monitoring and an incident procedure, in your environment or on our platform.

    Output: a product in operation

Services

In your environment or on our platform

We manage infrastructure in your environment, or run it on our platform. Technology is chosen to fit your applications and team.

What we do, specifically

  • Infrastructure modernisation and cloud

    Cloud, your own servers, or both – by cost, risk and operational effort.

    • Inventory. We list your servers, applications and how they depend on each other, who has access to what, and what running it all costs per month, in one overview.
    • Comparing options. Cloud, your own servers, or both. We weigh each on cost, risk, operational effort and how easy it is to leave later. You get a recommendation with the reasons.
    • Target design. We design the network, identity and access, backups and monitoring to fit your applications, team and budget.
    • Step-by-step move. We split the migration into smaller steps. Each has a test and a rollback procedure and is scheduled outside your peak hours, without a one-off switch-over of the whole environment.
    • Code and documentation. The result is brought into IaC and documented. The environment can be rebuilt at any time and remains yours after the engagement ends.

    For example: An application moves off an ageing server to the new environment piece by piece, without one big switch-over.

    More about the service

  • DevOps and automation

    New versions in production without manual steps, and a clear view of what runs where.

    • Deployment review. We look at how a new version reaches production today, what is done by hand and what slows it down. That tells us where to start.
    • Faster, cheaper delivery. We automate and speed up builds and tests to shorten deployment time and reduce build costs.
    • Containers. Applications are containerised so they run identically in development, test and production. Orchestration is added only when it pays off.
    • App overview. An overview of which version runs in which environment. Every change is recorded and can be reverted.
    • Safe rollouts. A new version reaches a small share of users first. On errors, the previous version is restored automatically.

    For example: Once a change is approved, tests, deployment and a check of the new version run automatically.

    More about the service

  • Security and technical assessments

    Priorities by risk, and controls put into practice.

    • Technical review. We review your infrastructure and development processes: access and permissions, network, updates, logging, backups and how deployments work. We look at how the systems really are, not only at the documentation. The output is a report of the findings.
    • Priorities. Findings are ranked by risk and effort: what to fix now, what later and what to accept as a risk. The output is a concise remediation plan.
    • Remediation. We put controls in place in production: multi-factor authentication (MFA), network segmentation into zones, patches, removing unused accounts, and encryption, with everyday work in mind.
    • Verification. Test restores of backups, access reviews and checks that alerts are delivered. Every control is verified, not assumed.
    • Evidence for audits and NIS2. We write down what is in place, how it is evidenced and who is responsible. We can then keep monitoring the state.

    For example: We remove former suppliers’ access, apply missing patches and check that backups actually restore.

    More about the service

  • Ongoing operations

    Monitoring, updates, backups and incident handling.

    • A foundation in code. Before taking over operations we bring the environment into IaC and document it. Every change is traceable and management does not depend on one person.
    • Monitoring. We track the health of infrastructure and applications so that problems are caught before users notice them. Alerts are handled within the agreed response times.
    • Updates. Systems and their dependencies are patched on a schedule, in agreed windows. Security patches are not put off.
    • Backups. Backups kept apart from production, regularly verified by test restores, with a known recovery time.
    • Incidents and reporting. Incidents are fixed, traced to their cause and followed up so they don’t repeat. A regular status and cost report is included.

    For example: A full disk or an expiring certificate is handled when the alert comes, not after an outage.

    More about the service

  • AI platform

    Company AI under control.

    • Mapping. We look at which AI tools are already in use, where data goes and who holds which keys. That tells us what to bring together first.
    • Company chat. Employees sign in with their company account and get approved models only. Model keys stay on the server, not with people.
    • One gateway to models. Applications and agents reach models through one controlled entry point: approved models, limits and budgets per team.
    • Visibility with Langfuse. A record of what applications and agents did, what they worked from, what it cost and whether the result was right.
    • Rules for data. We set which data may go where, where it is processed and how long it is kept. Sensitive agent actions need human approval.

    For example: An agent drafts a quote from an enquiry. You see which stock data it used, what it cost and whether sales approved it without changes.

    More about the service

in your environment

On your servers or in your cloud

The infrastructure stays yours. You decide the scope of the work.

  • New infrastructure (greenfield)From design to launch, all in IaC. We hand it over or run it for you.
  • Modernisation and migrationIn verified steps, each with a rollback.
  • DevOps and automationAutomated, repeatable deployment of new versions.
  • Security, NIS2 and ISO 27001Assessment, remediation, audit evidence.
  • Operations, monitoring and supportFull operations, or cover for your in-house administrator.
  • AI platformCompany chat, LLM gateway, agent oversight.

on our platform

Hosted on our platform

Applications run on our platform; we manage everything underneath. Included:

  • operations and monitoring
  • security scanning and alerts
  • updates and patching
  • backups with tested recovery
  • automated deployment of new versions
  • No servers of your own to run.
  • Your developers can deploy new versions to it directly.

Suited to companies without their own operations team. Before the move we standardise the environment and bring it into IaC; you own the code.

Combinations are common: part with you, part with us, or a gradual move.

Our standard

Part of every project

These are in place in every environment from day one. They are prepared in IaC and are not charged as extras.

  • Secure by design

    Least-privilege access, a segmented network, secrets in a vault, encryption. Continuously, not once a year.

  • Monitoring and alerts from day one

    Availability, performance and security events; we respond to the alerts.

  • Backups with verified restores

    Kept apart from production, regularly verified by test restores, with a known recovery time.

  • Infrastructure as code

    Everything in IaC and documented; management does not depend on one person.

  • Accounts and repositories in your name

    You own the code and data. The engagement can be ended at any time.

About

An experienced team you work with directly

ROKKA is a new company with an experienced team. You work directly with people who designed and ran systems in banking and critical infrastructure with continuous-availability requirements.

More about us

Principles

  • Only in areas we master

    If a request goes beyond our expertise, we say so and recommend a suitable partner.

  • Technology-independent

    Technology is chosen by requirements, team and budget.

  • Change only where it makes sense

    Cloud, your own servers or the current setup – by cost and risk. Leaving a solution unchanged is a valid recommendation.

Contact

Request a consultation

A short description of your environment and what you need solved is enough. We reply within one working day. If your team already covers operations, security and cover, we will tell you.

info@rokka.engineering

This opens your email app with the message ready to send.

We use the details from this form only to reply to your inquiry.