# Off-topic - 2021 plans for eramba

**URL:** https://discussions.eramba.org/t/off-topic-2021-plans-for-eramba/1714
**Category:** Forum - Software
**Created:** [October 29, 2020, 10:39am UTC](https://discussions.eramba.org/t/off-topic-2021-plans-for-eramba/1714 "2020-10-29T10:39:49Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![eramba](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/e/c6cbf5/32.png) [@eramba](https://discussions.eramba.org/u/eramba)
#### Post date: [October 29, 2020, 10:39am UTC](https://discussions.eramba.org/t/off-topic-2021-plans-for-eramba/1714/1 "2020-10-29T10:39:49Z")

</div>

every couple of months we plan or re-plan what we need to get done , our typicall deviation error when planning is in the order of “one or two months” at best but it does help us having a long term vision

 ![image](https://discussions.eramba.org/uploads/default/original/2X/2/2553fb9722984cb07d0742870ff52dfc1a74c0ff.jpeg)

Martin and Marek will work on migration, scalability and workflows until next spring.

- by December 2020 we need to complete the [migration](https://discussions.eramba.org/t/feature-cakephp-upgrade-massive-complex-and-uncertain/1489), is very likely we’ll do it by then
- by January we’ll start pushing the “[migration](https://discussions.eramba.org/t/feature-cakephp-upgrade-massive-complex-and-uncertain/1489)” eramba to customers, we expect two months to additionally stabilise.
- After all customers migrated to the new eramba, we’ll work on [scalability issues](https://discussions.eramba.org/t/feature-decouple-modules-into-multiple-slave-r-databases/1671/2) and [workflows](https://discussions.eramba.org/t/feature-bloody-user-defined-workflows/1114), some 4-6 months of work

Viktor will keep focusing on [opensourcegrc.org](http://opensourcegrc.org), we expect a solid BETA to be ready by late this year.

By April 2021, once scalability is addressed we can start offering [SaaS/Hosted](https://discussions.eramba.org/t/feature-eramba-saas/942) services, before that makes no point as the architecture will most likely change. We need further skills to design this setup and operate it, we’ll see how we manage that.

Our [roadmap](https://www.eramba.org/roadmap) is plagued with issues on both short and terms issues, the chart below is a quick analysis that shows we are really behind -the migration is to be blamed for this-. We plan to hire a new developer in eramba to focus on backend issues by January hopefully slowly working on them as he/she learns how we work. We are hoping to address half of the current queue by Spring.

 ![image](https://discussions.eramba.org/uploads/default/original/2X/9/91c306afda31ec0c41d711db66ba761d7db15635.png)

We’ll see how all this goes, is fun to write this things because we always read them and make laughs of how plans typically end up going over here.

 ![image](https://discussions.eramba.org/uploads/default/original/2X/a/afdd16ea7b89f3b48af2d1168a4090eb2d99833b.jpeg)