Question 1

Do you work with clients outside Pakistan?

Accepted Answer

Yes. We work with clients in the US and Netherlands alongside our Pakistan-based work, fully remote and async.

Question 2

Do you sign NDAs?

Accepted Answer

Yes. We have a standard NDA ready to sign before any project discussion if required.

Question 3

What happens after I send a message?

Accepted Answer

You'll receive a response within 4 hours during business hours (PKT / GMT+5). If your project is a good fit, we'll schedule a 30-minute discovery call.

Question 4

Do you offer free audits?

Accepted Answer

Yes. For Odoo infrastructure projects, we offer a free 30-minute audit call where we review your current setup and identify the top 3 issues.

Question 5

How many workers should my Odoo server run?

Accepted Answer

The starting formula is roughly one worker per CPU core plus one, with each worker budgeted around 1 GB of RAM, then adjusted for cron threads and how heavy your reports are. We measure before setting it, because an under-provisioned worker count and an over-provisioned one produce the same complaint from users.

Question 6

Do you work on Docker installs or service installs?

Accepted Answer

Both. Our own fleet runs a mix of Docker Compose stacks and systemd service installs across Flectra through Odoo 19, and each has cases where it is the better fit.

Question 7

Can you take over an instance somebody else built?

Accepted Answer

Yes, and it is the most common way clients start with us. The first step is always an audit so we know exactly what we are inheriting before changing anything.

Question 8

What if my Odoo version is old?

Accepted Answer

We support Flectra and Odoo 13 upward in production today. An old version is a valid reason to plan an upgrade, but it is not a reason to leave the current server untuned in the meantime.

Question 9

Which cloud provider do you recommend?

Accepted Answer

It depends on the workload, and we have production experience across AWS, Azure, DigitalOcean, Hetzner and Contabo. For a single-region Odoo instance a good VPS is usually the cheapest sound answer; the hyperscalers earn their premium when you genuinely need their managed services or regional footprint.

Question 10

Can you cut our cloud bill without downtime?

Accepted Answer

Often yes. Deleting orphaned volumes and snapshots, right-sizing over-provisioned instances during a maintenance window, and dropping managed services that duplicate what your server already does are the usual wins.

Question 11

Do you do multi-cloud?

Accepted Answer

Where there is a reason for it, such as keeping backups in a different provider from production. We do not recommend multi-cloud as a default, because it doubles the operational surface for most teams.

Question 12

What does the assessment report include?

Accepted Answer

A written document with current state, findings ranked by risk, a target architecture, cost comparison and a prioritised remediation plan you can execute with or without us.

Question 13

GitLab CI or GitHub Actions?

Accepted Answer

Whichever your code already lives in. We build both, and the pipeline structure we use is the same either way.

Question 14

Can you set this up for an Odoo instance?

Accepted Answer

Yes, and Odoo needs a couple of specifics: the module upgrade step and a filestore-aware backup before deploy. A generic web-app pipeline skips both and that is where Odoo deployments go wrong.

Question 15

Do we need Docker for this?

Accepted Answer

No. Containers make some steps cleaner, but a pipeline that deploys to a systemd service install works well and we run both in production.

Question 16

What happens if a deploy fails halfway?

Accepted Answer

The pipeline stops at the failed stage rather than continuing, the pre-deploy backup is already taken, and the rollback command returns the server to the previous release. That order is the point of the setup.

Question 17

How much downtime will we have?

Accepted Answer

We plan for none during business hours. The new server is built and validated in parallel, so the only switch is DNS, and the old server keeps serving until it propagates.

Question 18

We have a whole fleet, not one server. Does that change things?

Accepted Answer

It changes the sequencing, not the method. We have migrated an 11-server Odoo fleet this way, one server at a time with the runbook improved after each, which is also why fleet pricing is lower per server.

Question 19

What if something is wrong after cutover?

Accepted Answer

The old server is deliberately kept running for a holdback period, so a rollback is a DNS change and not a rebuild. That is written into the plan before we start.

Question 20

Do you migrate Windows or MSSQL workloads too?

Accepted Answer

Yes. Most of our work is Linux and PostgreSQL, but we run production Windows and MSSQL workloads for clients as well.

Question 21

Can we jump several versions at once, for example 14 to 19?

Accepted Answer

Yes. Odoo's upgrade tooling supports going straight to a target version without stepping through every release in between, and multi-version jumps are common in our work.

Question 22

How long does an upgrade take?

Accepted Answer

A lightly customised instance is about a week. Heavily customised instances with many integrations typically need six to eight weeks, most of which is testing rather than the upgrade itself.

Question 23

Will our customisations survive?

Accepted Answer

Each one is reviewed and categorised first. Some carry over untouched, some need refactoring for API changes, and occasionally something is better replaced by a native feature the new version added. Nothing goes live untested.

Question 24

What about our Odoo Studio and no-code customisations?

Accepted Answer

Those are database records rather than code, so they migrate with the database, but they still need testing, because underlying view and field changes can affect them.

Let's build something that lasts

Where We Work

Before you message

Do you work with clients outside Pakistan?

Do you sign NDAs?

What happens after I send a message?

Do you offer free audits?

How many workers should my Odoo server run?

Do you work on Docker installs or service installs?

Can you take over an instance somebody else built?

What if my Odoo version is old?

Which cloud provider do you recommend?

Can you cut our cloud bill without downtime?

Do you do multi-cloud?

What does the assessment report include?

GitLab CI or GitHub Actions?

Can you set this up for an Odoo instance?

Do we need Docker for this?

What happens if a deploy fails halfway?

How much downtime will we have?

We have a whole fleet, not one server. Does that change things?

What if something is wrong after cutover?

Do you migrate Windows or MSSQL workloads too?

Can we jump several versions at once, for example 14 to 19?

How long does an upgrade take?

Will our customisations survive?

What about our Odoo Studio and no-code customisations?

Let's build something that lasts

Where We Work

Before you message

Do you work with clients outside Pakistan?

Do you sign NDAs?

What happens after I send a message?

Do you offer free audits?

How many workers should my Odoo server run?

Do you work on Docker installs or service installs?

Can you take over an instance somebody else built?

What if my Odoo version is old?

Which cloud provider do you recommend?

Can you cut our cloud bill without downtime?

Do you do multi-cloud?

What does the assessment report include?

GitLab CI or GitHub Actions?

Can you set this up for an Odoo instance?

Do we need Docker for this?

What happens if a deploy fails halfway?

How much downtime will we have?

We have a whole fleet, not one server. Does that change things?

What if something is wrong after cutover?

Do you migrate Windows or MSSQL workloads too?

Can we jump several versions at once, for example 14 to 19?

How long does an upgrade take?

Will our customisations survive?

What about our Odoo Studio and no-code customisations?