Solutions
IT solutions for specific business needs
Every solution starts from a real problem faced by management or an IT manager, and explains which architecture solves it, which Seintec services are involved and how it is deployed without stopping day-to-day operations.
Solutions group several services around one need: keeping an ERP available, working outside the office securely, recovering after an incident or connecting multiple sites. If you are looking for the technical detail of a single service, the services catalogue describes the scope, operation and support of each one.
- ERP and business applicationsBusiness ERP in the cloudWe move your ERP and its databases to managed cloud infrastructure, with backup, performance and remote access resolved, coordinating with your software vendor.
- Business softwareHosting for A3, Sage, AHORA and OdooWe host and operate the infrastructure where your business software runs, always subject to compatibility, licensing and coordination with the software provider.
- Workplace decisionHow to implement virtual desktops in a businessA decision guide to identify which users and applications should be centralised, which model fits and how to validate the change before a company-wide rollout.
- Remote accessSecure remote work for companiesOrderly remote access: who connects, from where, to which applications and under what control. Without opening ports or handing out unrecorded access.
- VirtualisationMigrating away from VMwareOptions for companies reviewing their virtualisation: moving machines to our managed cloud or rethinking the platform on owned hardware, with inventory and testing before touching production.
- ContinuityBusiness continuityDefining which processes cannot stop, how long each one can be out of service and which infrastructure and procedures support that.
- Data protection strategyHow to design a business backup planA guide to deciding what to copy, how often, for how long and how to verify recovery before selecting a backup platform.
- Multiple sitesIT infrastructure for multi-site companiesOne platform for every branch: centralised applications, an interconnected network and a single point of contact for the whole operation.
- SecurityCybersecurity for small and medium companiesProportionate, sustainable measures: protecting email, endpoints, access and backups, with continuous monitoring and a clear procedure for when something goes wrong.
- IndustryIT infrastructure for industrial companiesPlant and office have different needs. We design the corporate network, the servers and continuity knowing that production cannot be stopped at will.
- Architecture decisionPrivate cloud versus public cloudA practical comparison to decide where each workload belongs: predictable performance, data control, stable cost and who operates the platform.
- IncidentsRecovering after ransomwareWhat to do when systems are encrypted: contain, assess the scope, recover from reliable backups and rebuild an environment that will not fall the same way again.
- Infrastructure decisionWhen to choose a managed dedicated serverCriteria for deciding whether a workload needs exclusive hardware or is better suited to cloud, and how to size and migrate without guessing at capacity.
- Datacenter relocation projectHow to move servers to a datacenter in BarcelonaCriteria and stages for moving owned hardware out of the office, calculating space, power and connectivity, and controlling the downtime window.
How to decide where to start
Start from the problem, not from the technology
Every solution on this page begins with a specific situation: an ERP that slows to a crawl at month end, a site that loses its connection, backups nobody has verified, a virtualisation contract whose price keeps rising, or a team that needs to work away from the office without exposing the network. Naming the problem first avoids buying product before understanding what has to be fixed, which is the usual origin of infrastructure that is expensive and hard to maintain.
Inventory and measurement before any decision
Before proposing a change we look at what exists: servers and their real consumption, operating systems and versions, licences, communication lines, backups and their results, remote access and the dependencies between applications. That inventory has value in itself, because it exposes reserved capacity nobody uses, unpatched machines and the points where the business stops if a single component fails. The decision that follows rests on data from the environment rather than on assumptions.
Phased change with a way back
Projects are planned in phases with an agreed window, a defined start-up order and a rollback plan should anything behave unexpectedly. Work begins with a pilot group or a single site, the standard that works is documented, and it is then replicated elsewhere. Investment is staged and each step is tackled with a configuration already proven in production, instead of a simultaneous rollout that cannot be reversed.
Ongoing operation and review
A solution is finished when it is being operated: monitoring of services and resources, updates, access management, backups with agreed retention and restore tests with measured timings. Periodic reviews cover unpatched machines, accounts without multi-factor authentication, backup results and incidents in the period, each with an action and a date. Without that part, any improvement degrades within a few months.
Frequently asked questions about these solutions
- What is the difference between a solution and a service?
- A service describes a single capability — backup, support, cybersecurity, connectivity. A solution combines several services to resolve a complete business situation, with a defined order of work and clear objectives. It is common to arrive through the solution and then contract only the services that are missing, because part of the environment is already covered.
- Does everything have to change at once?
- No, and it is rarely advisable. The usual route is to tidy up whatever causes the most incidents or the most risk, document it and move on from there. Many projects start with backup and recovery, because they are the safety net for everything else, and continue with connectivity, servers or workstations depending on what weighs most day to day.
- Can part of the current infrastructure be kept?
- Yes. Hybrid environments are common: on-premises servers alongside managed cloud infrastructure while the hardware is written down, or while a specific application cannot be moved. What matters is that the coexistence is designed, with consistent networking, backup and access on both sides, rather than being the by-product of a half-finished migration.
- How are scope and cost agreed?
- Through a prior review of the environment and a proposal setting out what is included, what is not, the intervention windows and the contact channels. Scope is written into the service contract so that it does not rest on habit. If the review turns up something better dealt with first, it is flagged separately so the company can decide the order.