Skip to content
Updates and versions

Always on a current version, without ever running an upgrade

Self-managed software drifts. A version behind becomes four versions behind, and then an upgrade is a project. Managed Cloud keeps you current release by release, so the gap never opens.

In short

  • Applied for you
  • Tested first
  • Scheduled with you
  • Reversible
What the service does

Software updates and versions

Every new Stockovaa release is applied for you, on a window we agree, after it has been checked against your configuration. Nothing to download, nothing to schedule around month end.

Every release, applied by us

New features, fixes and security releases reach your account as part of the service. There is nothing to download and no upgrade project to budget for.

Checked against your setup first

Your configuration, your integrations and your customisations are considered before an update is applied, rather than after it has broken something.

Scheduled around your trading

Updates land in a window we agree with you. Not during your Saturday rush, and not on the last day of the month while you are closing your books.

Reversible if it goes wrong

A backup is taken before an update is applied, so returning to the previous state is a decision rather than a disaster.

You are told what changed

Each update comes with a plain summary of what is new and anything your team will notice. Staff should not discover a changed screen mid transaction.

Help with what is new

If a release adds something your business would benefit from, we will point it out and walk your team through it rather than leaving it undiscovered.

In scope

What update management covers

The whole stack, not just the part with a version number in the footer.

  • Stockovaa feature releases and fixes
  • Security releases, treated with more urgency than feature work
  • Database migrations, applied additively so existing records are never dropped
  • Everything the platform runs on underneath, kept in supported versions
  • A record of which version your account is on and when it last changed
How it works

How an update reaches you

Four steps. You are involved in one of them.

  1. The release is reviewed

    We read what changed and decide what it means for accounts like yours before anything is scheduled.

  2. It is tested against your configuration

    Your setup is not the default setup. The update is checked against how your account is actually configured.

  3. We agree the window and take a backup

    You are told when it is happening. A copy of your data is taken immediately beforehand as a matter of routine.

  4. It is applied and confirmed

    We apply it, check the result, and tell you what changed. If something is wrong we go back and start again rather than leaving you on a broken version.

The point of it

What your team never has to do

  • Decide whether an update is safe to install
  • Run an upgrade after hours and hope
  • Live three versions behind because the last upgrade hurt
  • Explain to staff why a screen changed overnight with no warning
Questions

Asked and answered

If yours is not here, ask us directly. We would rather have the conversation than have you guess.

You can ask us to defer a feature release and we will discuss timing with you. Security releases are different: we apply those, because leaving a known problem in place on a system we manage is not something we are willing to do.

That is exactly what the testing step is for. Your configuration is checked before an update is applied, and there is a backup immediately beforehand so a bad outcome is reversible.

No. Being on a current version is the service. Your lifetime licence covers the software and Managed Cloud covers the work of keeping it current.

The updates page in your portal shows your current version, when it was applied, and a summary of what each release changed.

See the whole service

This is one part of Managed Cloud. The rest of it works the same way: our team does the work, and your team gets on with trading.