Websome Services
DevOps Support in ERP Projects
In an ERP project, preparing the software isn't enough – it also needs to be deployed and released to the client. We support implementation teams in this area: we deploy add-ons and integrations, configure deployment pipelines and ensure changes reach the production environment in an orderly manner. We use Docker among other tools.
Why choose us
- ✓CI/CD pipeline configuration for ERP add-ons
- ✓Docker and containerisation for ERP environments
- ✓Automated tests before production deployment
- ✓Zero-downtime deployments for critical systems
- ✓Kubernetes / OpenShift
- ✓Including ERP systems (enova365 / Odoo)
Standards
- Separate DEV/UAT/PROD environments with periodic rebuild and proper isolation
- Procedures for testing, system updates, launch, restore, environment handover and more
- Automation of every process related to software delivery
- Workflows for development teams ensuring quality and security
- Keeping teams informed about ongoing test work and system availability
When it's useful
When an add-on or integration needs to be deployed to the client's ERP environment safely and in a controlled manner.
When the implementation team has no one to handle deployments, pipelines and environment management.
When changes to the ERP system and its add-ons need to go through a structured, documented and reversible process.
Who it's for
When DevOps support is needed in the ERP project and you don't have that expertise in-house.
When a development or integration project around your ERP requires support in launching, testing and deploying changes.
Typical deployment patterns
ERP as the master data source, with event-driven pipelines (Azure Service Bus, AWS SQS, RabbitMQ) synchronising data to external systems. We deploy, monitor and maintain the integration layer.
Web applications and B2B portals reading data directly from ERP databases or APIs — displaying orders, documents, inventory and other records for external users.
Dedicated tools for managing, auditing and migrating ERP data — built to handle the specific structure of enova365, Odoo or Comarch databases.
Experience with self-hosted ERP instances, hybrid cloud setups and non-standard deployment configurations — we're comfortable where generic playbooks don't apply.
How we work
You describe the need
Tell us which ERP you're working with, what you need to deploy and what the current environment looks like.
We design and quote
We define the scope and approach. You receive a quote and schedule.
We deliver
We complete the agreed scope: pipelines, containerisation, deployment scripts — keeping you updated on progress.
We deploy and support
We launch the solution on the target ERP environment and remain available after deployment for fixes and further iterations.
Frequently asked questions
Which ERP systems do you support?
We have hands-on experience with enova365, Odoo and Comarch environments. We also work with custom ERP systems and integration layers built on top of them — including cloud queue integrations (Azure Service Bus, AWS SQS, RabbitMQ).
How does ERP DevOps differ from standard DevOps?
ERP systems have specific installation and update requirements, often run on Windows Server with MSSQL, and have vendor-defined upgrade procedures. We understand these constraints and work within them — rather than applying a generic containerisation approach that doesn't fit. A good example is the RDP administrative workstation — something a "pure-code" developer would avoid at all costs.
How is the service billed?
Within the project scope or at an hourly rate. After describing the need, we prepare a quote.