Skip to content
BLAST SOFTWARE// S.R.O.

Services

Software engineering and IT services, scoped to be contracted

BLAST software, s.r.o. sells four defined services. Each entry below states what it includes, what you receive at the end, the technologies involved and how the engagement is shaped commercially.

Web, mobile and enterprise systems

Custom Software Architecture & Engineering

Business systems built to a written specification — domain model, architecture, implementation, automated tests, deployment pipeline, and handover of the complete source code and its documentation.

Included

  • Domain modelling and a written technical specification before implementation starts
  • Architecture decision records, so every structural choice has a stated reason
  • Web applications, internal enterprise systems, REST and GraphQL back ends
  • Native-shell and cross-platform mobile clients where a browser is not enough
  • Automated test suites, CI, and a repeatable deployment pipeline from day one
Full detail on Custom Software

What you receive

  • Written specification and architecture document
  • Complete source code in your own repository
  • CI/CD pipeline and environment configuration
  • Automated test suite and its coverage report
  • Operations runbook and developer onboarding notes

Engagement

Fixed-scope phases against a written specification, or monthly retained delivery.

Discovery 2–4 weeks; delivery phases sized to the agreed specification.

Technologies

  • TypeScript
  • React
  • Node.js
  • PHP 8.3
  • Java
  • Python
  • PostgreSQL
  • MySQL
  • Docker

Independent technical assessment

IT Advisory & Digital Transformation Consultancy

An independent read on the systems you already run: architecture review, build-versus-buy analysis, technical due diligence and a costed, prioritised roadmap — delivered as a written report you keep.

Included

  • Architecture and code review against the load and the roadmap you actually have
  • Build-versus-buy analysis with the assumptions written out so you can challenge them
  • Technical due diligence for investment, acquisition or vendor selection
  • Delivery-process review: branching, environments, release cadence, on-call
  • A prioritised roadmap with effort bands, dependencies and stated risks
Full detail on IT Consultancy

What you receive

  • Written assessment report with findings ranked by impact
  • Prioritised remediation roadmap with effort bands
  • Risk register covering technical, operational and vendor risk
  • Walkthrough session with your engineering and executive teams

Engagement

Fixed-fee assessment, or a retained advisory day per sprint.

Assessments are normally scoped between 1 and 6 weeks.

Technologies

  • Architecture review
  • ADRs
  • C4 model
  • Threat modelling
  • Cost modelling

Infrastructure as code, systems that talk to each other

Cloud Infrastructure, DevOps & System Integration

Infrastructure defined in code, pipelines that deploy without ceremony, and integrations between ERP, CRM, payment, logistics and identity systems where retries, idempotency and reconciliation are designed in rather than discovered in production.

Included

  • Infrastructure as code on AWS, Microsoft Azure or a European provider of your choice
  • Containerisation, orchestration and zero-downtime release strategies
  • CI/CD pipelines with automated tests, migrations and rollback
  • System integration: ERP, CRM, payments, logistics, SSO and identity providers
  • Observability — structured logs, metrics, tracing and alerting that names an owner
Full detail on Cloud & DevOps

What you receive

  • Terraform or equivalent infrastructure definitions in your repository
  • Deployment pipeline with a documented rollback path
  • Integration contracts, message schemas and a reconciliation procedure
  • Monitoring dashboards and an alert routing policy

Engagement

Project-based platform build, or a monthly platform-engineering retainer.

Platform builds typically run 4–12 weeks before handover.

Technologies

  • AWS
  • Azure
  • Kubernetes
  • Docker
  • Terraform
  • GitHub Actions
  • Prometheus
  • Grafana

Strangle the monolith, fix the queries

Legacy Modernisation & Database Optimisation

Incremental modernisation of systems that still earn their keep: characterisation tests first, then a strangler-fig migration, schema and index work, query optimisation and a data migration you can roll back.

Included

  • Characterisation tests that capture current behaviour before anything moves
  • Strangler-fig migration — the old system keeps running while modules move out
  • Schema redesign, indexing strategy and query-plan analysis
  • Data migration with dry runs, reconciliation reports and a rollback plan
  • Upgrade paths for end-of-life runtimes, frameworks and database versions
Full detail on Legacy & Data

What you receive

  • Characterisation test suite over the existing behaviour
  • Migration plan with sequenced, independently revertible steps
  • Before-and-after query plans for the workloads we were asked to improve
  • Data migration scripts, dry-run output and rollback procedure

Engagement

Phased fixed-scope migration, or an embedded engineer alongside your team.

Phased over months; each phase independently releasable and revertible.

Technologies

  • PostgreSQL
  • MySQL
  • MS SQL Server
  • Oracle
  • Redis
  • Elasticsearch
  • PHP
  • Java
  • .NET

How an engagement runs

From first enquiry to handover, with nothing opaque in between

The same five stages every time. You can stop after any of them, and what has been produced up to that point is yours.

  1. 01

    Discovery call

    A scoping conversation with an engineer. We establish the problem, the constraints, the systems already in place and whether we are the right supplier at all.

  2. 02

    Written proposal

    Scope, architecture direction, delivery phases, team composition, assumptions and exclusions — in writing, and priced only once the scope is agreed.

  3. 03

    Contract and kickoff

    A signed contract with a named statutory representative, a data processing agreement where personal data is involved, and access set up on your side.

  4. 04

    Iterative delivery

    Two-week increments, demonstrable software at the end of each, and your own repository from the first commit. No opaque phases.

  5. 05

    Handover and support

    Source code, documentation, runbook and a walkthrough. Ongoing support only if you want it, under a separate agreement you can end.

Not sure which of the four it is?

Most real projects are two of them at once. Describe the problem and we will say which shape it takes — or tell you it is not work we should be doing.

Request Solution QuoteTalk to an engineer