Skip to main content

Business software

Hosting for A3, Sage, AHORA and Odoo

We host and operate the infrastructure where your business software runs, always subject to compatibility, licensing and coordination with the software provider.

The starting point

A3, Sage, AHORA and Odoo are installed in very different ways depending on edition, version and modules. Hosting them properly is not about moving a server: it is about reviewing which components exist, who maintains them and which licensing terms apply.

What we usually find

  • Old versions that constrain the operating system or the database engine.
  • Modules, custom development or integrations nobody has documented.
  • Uncertainty about what the software reseller maintains and what the IT provider does.
  • Databases that grow unchecked and slow every user down.

Which companies it fits

Companies, accounting and advisory firms running these applications on their own server that want managed infrastructure without changing software.

Tell us which software and version you use and we will review technical feasibility before proposing an architecture.

Check compatibility

What the solution includes

  • Compatibility review first

    Edition, version, modules, custom development and database engine before committing to anything.

  • Properly sized platform

    Cloud servers or private cloud with resources matched to concurrent users and processes.

  • Backup and retention

    Encrypted backup of data and databases, with restore tests.

  • Coordination with the maintainer

    We work with the software reseller or partner on installations, versions and application support.

How it is deployed

  1. 1Inventory of the current environment and software contracts.
  2. 2Requirement confirmation with the software provider.
  3. 3Environment preparation and test copy.
  4. 4Migration in an agreed window with key-user validation.
  5. 5Operation, monitoring and ongoing support.

Real-world scenarios

An accounting firm with many client databases

In practices and advisory firms the management software often holds dozens of databases, one per client, growing every financial year. Performance degrades gradually and becomes obvious during filing periods. Sizing is based on concurrent users and real data volume, and backups are scheduled so they never overlap with closing routines.

An older release that dictates the operating system

It is common to find an edition supported only on a specific Windows Server version or a database engine that is out of maintenance. Before anything moves, the supported combination is confirmed with the software reseller. If the vendor does not support the target platform, we say so and propose the upgrade as a prior step.

Division of responsibility with the reseller

Seintec takes care of the platform: server, operating system, database, backups, access, perimeter security and end-user support for anything affecting the workstation or the connection. The software reseller maintains functional updates, application issues and licences. During onboarding it is agreed who raises each type of incident, what information is supplied and how it escalates when the cause is unclear. That agreement avoids the loop common in professional firms, where the company ends up mediating between two providers.

What is at stake if it is left unaddressed

  • Undocumented customisations

    Reports, automations or integrations built years ago can stop working after a server change if they are not inventoried beforehand.

  • Licences tied to the machine

    Some licences activate against hardware or the server name. The reactivation procedure should be confirmed with the reseller before the change window.

  • Uncontrolled database growth

    Without maintenance or archiving of historical data, the database ends up dictating performance for every user and the length of every backup.

Frequently asked questions

Is Seintec a partner or reseller of these vendors?
We make no such claim. Seintec operates the infrastructure where the software runs and coordinates with the provider that maintains it.
Can any version be hosted?
Not always. Some versions require specific systems or are not supported by the vendor in external hosting; we check case by case.
How is this different from the SaaS versions?
In SaaS the vendor hosts and operates the application. Here we refer to self-installed deployments, where infrastructure is the customer's or their IT provider's responsibility.
Can we keep our current IT provider?
Yes, when the customer prefers it. Responsibilities are set out in writing to avoid grey areas.
Is Seintec a partner or reseller of A3, Sage, AHORA or Odoo?
No. Seintec holds no accreditation from those vendors and does not sell their licences. What we provide is the infrastructure the software runs on and its day-to-day operation: servers, backups, security, remote access and end-user support, working alongside the reseller that maintains the application.
Can people use these applications from outside the office?
Yes, usually by publishing the application through a remote desktop or via VPN access with multi-factor authentication, depending on what the software supports. The pilot phase tests printing, spreadsheet export, signing and scanners, because those are the tasks that cause trouble when they are not validated with real users first.
What happens if we change management software later?
The infrastructure is not locked to the software. If the company moves to a different application, the environment is adapted to the new requirements and the previous data is retained according to the agreed policy, which matters where tax or document retention obligations apply.
How are peak periods handled?
They are identified during initial sizing: quarterly closes, tax filing deadlines or year-end. In those weeks planned interventions are avoided, resources are reviewed in advance and backup windows are adjusted so they do not overlap with the processes that load the database most heavily.

Check compatibility

Tell us which software and version you use and we will review technical feasibility before proposing an architecture.

Check compatibility