Why we built SPYN


After doing dozens of odoo projects, and showing demos of odoo to many many sales prospects, we realized that it’s a minor pain in the neck to install it each time.

Salespeople had to chase developers to provide a demo, often with special features they want to impress a prospect with.

We had the next problem when we won a new project: to install odoo from scratch, configure it for German business, load already available modules, and prepare the system finally for new development, not to mention, install a staging machine, and finally a production machine.

 Each time, the installation looked a little different. This means there was no standardization. And each time we had to install piece by piece by hand. This means there was no automation.

We decided to solve this problem by developing a simple robot that: 

  1. allows for the deployment of odoo, all necessary modules, and 

  2. configure it in a standard way.

So for example, once set up, SPYN

⇢ deploys odoo within minutes in the German language,

⇢ with specific decimal & thousands separator,

⇢ loaded with specific standard modules,

⇢ load them with specific config variables,

⇢ install the database

⇢ install the demo-data

⇢ configure the web-server, and

⇢ finally mail username/password along with the https:// link to a user (could be a sales guy, prospective customer, or a developer).

The benefits have been amazing.

 Salespeople can organize demos for prospects within minutes, with the latest code & features of every GIT-committed module.

 Quickly get an installation (preloaded with all our standard modules) for training customer-users and our own employees.

Developers save huge amounts of time by skipping repetitive tasks, and these days get straight to their innovative tasks.

Why we built SPYN
Nikola R. 15 September, 2021
Share this post
Odoo on Private Cloud