Back ends that support business processes
We build the server side of business systems on PHP and Symfony. That covers workflows, CMS, e-commerce, CRM and ERP links and the admin tools people work in every day. We also run what we build.
What we build
-
Workflows and internal systems
Requests, approvals, routing by category and role. The process a company runs on paper or email, moved into one system.
-
Content and publishing systems
An editorial CMS with article types, media, scheduling and permissions, serving portals and apps through an API.
-
E-commerce and PIM
Catalogues, prices, orders, payments and product data management, in sync with the company's ERP.
-
Admin tools
Registries, reference data, users and roles. We build admin screens on a ready framework and spend the time saved on the parts that are specific to the business.
Work
-
Lasi.lv
An editorial CMS, subscriptions and CRM integration for a national publisher.
Read the case study: Lasi.lv -
Sils
A webshop, PIM and B2B ordering on one platform, synced with the ERP.
Read the case study: Sils -
Livonia Print
An employee request portal with routing by category and staff data from the ERP.
Read the case study: Livonia Print
How we work
We work by Agile and Scrum: work runs in sprints, and each sprint ends with a demonstration of working software on a staging environment. You see the system grow, and you can change direction after any sprint.
A task is started when its acceptance criteria are written and its dependencies are known. It is closed when it is implemented, tested, reviewed by a second engineer, shown on staging and approved by the client.
How we keep quality
We check every change automatically first, and then people review it.
-
Automated tests
On every change we run unit tests for business logic and integration tests for the database, queues and outside services.
-
Static analysis
Before a person reads the code, we check it automatically for type errors and coding standard.
-
Code review
We have a second engineer review every significant change before it is merged.
-
Database migrations
We change the database only through versioned migrations.
-
Controlled releases
We release to production only after approval, and always with a tested way back to the previous version.
Data
Most business data belongs in a relational database, and we use MySQL or PostgreSQL for it. Where a project needs it we add vector search with pgvector, a document store or Redis for cache, sessions and queues.
Running it after launch
A back end has to be watched. We deploy with Docker and CI/CD, keep development, staging and production apart, and monitor production with Zabbix.
Public systems sit behind a web application firewall and a CDN. After launch we stay on for updates, security fixes and further development.
Related services
A back end rarely stands alone. It talks to other systems through APIs and shows its data in a web interface.
Does a business process need a system of its own?
Tell us how the process works today and where it slows down.