Skip to content
Language
DE EN FR
Start a project
Start a project Service desk

Platforms that carry processes

Online platforms, portals and business applications, developed with agile methods on the cloudtec Stack. Prototype and finished platform come from the same team, which then also takes responsibility for operations.

Discuss your project How we develop

The illustration shows a branch graph: two side branches split off from the main branch and merge back into it, and the graph ends in a highlighted release point.

Starting point

Development on the cloudtec Stack

We have built on Symfony since 2013. Around 60% of a typical platform comes ready-made from the cloudtec Stack from day 1: user management, API layer, roles and hosting. You invest in the logic that defines your business.

Abstract graphic: three green squares of light in a row, from a dashed outline to a brightly glowing surface.

Rapid prototyping

Clickable prototypes in days, the first working ones in a few weeks. Iterative implementation with regular reviews shows you continuously what is finished and what comes next.

Abstract graphic: a cyan line of light moving forwards in three loops, each slightly brighter than the one before.

Agile development

In small steps we clarify the scope, develop, check the result with you and deploy. Requirements are prioritised continuously, not fixed once and then worked through.

Abstract graphic: a bright violet beam, enveloped from the start by a wider band of light.

ISO/IEC 27001 from the start

Security requirements feed into every architecture decision. The ISMS covers development, hosting and operations as one continuous process.

Platform types

What we develop

The stack is suited to different types of platform. What they all have in common: modular architecture, an API-first approach and long-term operations as an integral part.

Partner portal with orders, invoices and documents. The settings are locked because the ‘Partner’ role only sees what it is allowed to.

Web portals

Protected areas that an organisation offers its customers, partners or employees: with roles, permissions and individual business logic.

A shared platform with three tenants attached: a cantonal portal, a specialist office and a municipality, each with its own domain and its own languages.

Multi-tenant platforms

Many websites on one shared foundation. Each tenant has its own domains, languages, content and permissions, and no other tenant sees its data.

A hospital and a practice register patients with two Spitex organisations via a shared platform. One has accepted the registration, the other is still reviewing it.

Industry platforms

Platforms that connect an entire industry: registrations between hospitals and Spitex organisations, applications between interested candidates and employers, competitions from club to federation. Many organisations and roles, one shared process.

The flow of an order in four steps: receipt and review are done, approval is in progress, shipping follows. Processing runs asynchronously in the background.

Workflow and automation tools

Process automation with Symfony Messenger and an event architecture. Asynchronous processing for reliable business processes.

A legacy system and the new platform side by side, connected by an arrow. During parallel operation, the data is transferred with validation.

Replacing legacy systems

We replace legacy systems step by step, with parallel operation during the migration instead of big-bang risk. We migrate data with validation.

Three stages on a rising line: MVP, expansion and production, all on the same architecture.

MVP to production

From minimum viable product to scalable platform. The same architecture in every phase, nothing thrown away after the proof of concept.

Integration

Connect systems, make data usable

Specialist applications rarely work in isolation. The stack is the integration layer in between: it connects your systems via documented interfaces and brings together data from all sources.

Third-party systems and data sources

SAP, Abacus, Microsoft Dynamics, industry-specific systems, databases or JSON and XML feeds: we connect to wherever your data lives and in whatever format it comes. The exchange runs in both directions, with error handling instead of manual exports.

REST APIs with OpenAPI

With API Platform from the same codebase as the application: automatically documented as OpenAPI, versioned and secured via OAuth2/JWT. We assign access rights per endpoint and role, compliant with ISO/IEC 27001 and with audit logs.

Middleware & asynchronous processing

RabbitMQ, Symfony Messenger and Azure Service Bus for reliable enterprise messaging. Transformation, protocol translation and routing in one place.

Preparation and transformation

Clean, map, normalise, enrich. Raw source data becomes consistent records, with validation and documented rules instead of fragile ad hoc scripts.

Data migration

Structured transfer of data from legacy systems: validation, mapping and transformation rules as a documented process, not as a one-off script.

Forwarding & display

Data is rarely where it is needed. Processed data goes to downstream systems or becomes directly usable: dashboards, reports and live views, consolidated from all connected sources.

Quality assurance

Not testing a lot, testing the right things

We specifically safeguard business-critical processes such as the basket in the shop or the approval in the portal, before an error costs revenue or trust. To do this, each level checks only what it changes itself.

Automatically with every change

Every change to the stack goes through unit tests, static analysis and automated scenarios for processes such as login, forms and the editor, many of them in the browser. Only when everything is green does it move on.

Only what your project changes

What the stack already covers, we do not test twice. Your platform checks its own functions and customisations, on staging before every go-live and afterwards in operation with smoke tests and monitoring.

What machines cannot judge

We check new components against the design and operation with keyboard and screen reader by hand, plus exploratory testing. For major changes, you carry out the acceptance yourself.

Findability

A platform nobody finds has no effect

We consider findability from the start: for classic search engines and for AI systems that read, summarise and cite content.

  • Technical SEO: clean semantics, structured data and fast delivery, built in from the start rather than optimised afterwards.
  • AI optimisation: clear structure, machine-readable summaries and clean metadata, so that language models capture content correctly.
AI in the stack
Product page of Beispiel AG for an 8 mm solid carbide milling cutter. In front of it, the matching search result with rating, price and availability from the structured data. A ‘Findability’ card confirms structured data, language versions DE and FR, a summary for AI and a loading time of 0.8 seconds.
Case studies

In production, for years

Three platforms that came about this way, with roles, interfaces and data flows at their core.

Healthcare · Platform

e-health platform OPAN®

Referral platform for aftercare: hospitals, practices and private individuals register patients with Spitex, care homes and clinics and see available capacity.

View case study: OPAN® e-health platform
View all case studies

Your platform deserves a foundation

Whether it’s a first idea or a concrete set of requirements: talk to our development team.

Platform configurator Put your stack together step by step and get an initial assessment. Book a live demo Start a project