The Openbravo Cloud is a single-tenant Infrastructure as a Service (IaaS) option that enables companies to deploy Openbravo products on virtual servers in Amazon Web Services (AWS), rather than in their own data center. This option is great for companies who want to retain control over the application but without the IT investments.
Thanks to Openbravo Cloud you can free yourself from the complexities and costs of managing hardware for your Openbravo solution, which can be scaled up or down based on growth or changing business needs. Additionally, Openbravo Cloud enables Openbravo to ensure the highest levels of security, availability, and performance.
Openbravo Cloud can be only subscribed in combination with a commercial edition of either the Openbravo Commerce Suite or the Openbravo Business Suite.
The Openbravo Commerce Cloud and the Openbravo Business Cloud are the result of the combination of the Openbravo Commerce Suite or the Openbravo Business Suite with the Openbravo Cloud.
With Openbravo Cloud customers get:
We will provide you with a URL to your Openbravo solution in the cloud, accessible from any web browser on any device with an Internet connection.
For maintenance activities, the system can also be accessed through SSH by you, your Openbravo Partner or Openbravo.
Unless otherwise agreed, Openbravo Cloud services are offered to you via designated members of your Openbravo Partner staff identified to Openbravo as your Technical Support Contacts for the purpose of the Subscription in the Openbravo Subscription Agreement.
Openbravo Cloud services include:
The AWS cloud is one of the most flexible and secure cloud computing environments available today and combines comprehensive security capabilities to satisfy the most demanding information security requirements. Openbravo follows AWS best security practices, ensuring that your data is safe. Customers retain ownership of any data stored in the AWS cloud. AWS does not access customer data. Partners and Openbravo can only access customer data according to the software subscription and support service terms signed by the customer. Users in the Openbravo application or access given to others for SSH is managed by the customer and/or partner.
Openbravo Cloud leverages AWS to ensure we provide the world's best cloud infrastructure with Openbravo Cloud. AWS follows strict guidelines and uses state-of-the-art architectural and engineering approaches to guard against physical and environmental threats. It has extensive experience in designing, constructing and operating large-scale datacenters. Physical access is strictly controlled, both at the perimeter and at ingress points by security staff and video surveillance. There are also fire detection and suppression, power, climate and temperature, and electromechanical support systems.
Openbravo Cloud Operations may carry out scheduled maintenance, or in rare circumstances, unscheduled maintenance. These activities may include changes to cloud hosting infrastructure, system software stack, and supporting application software to maintain operational stability, availability, security, performance, and currency of the Openbravo Cloud. All these activities are designed to minimize service interruption during the implementation of changes.
Openbravo reserves specific maintenance periods for changes that may require the cloud Service to be unavailable during the maintenance period. Openbravo works to ensure that change management procedures are conducted during scheduled maintenance windows, while taking into consideration low traffic periods and geographical requirements. The typical scheduled maintenance period is once a month on a Monday, initiating at approximately at 22:00 data center time, and lasting usually less than 1 hour.
Openbravo will work to provide prior notice of modifications to the standard maintenance period schedule.
For changes that are expected to cause service interruption, Openbravo will work to provide prior notice of the anticipated impact. The durations of the maintenance periods for planned maintenance are not included in the calculation of Unplanned Downtime minutes in the monthly measurement period for System Availability Level. Openbravo uses commercially reasonable efforts to minimize the use of these reserved maintenance periods and to minimize the duration of maintenance events that cause service interruptions.
Product software (Openbravo itself) changes are managed by the Openbravo Partner as per its contract with the customer and are excluded from the scope of Openbravo cloud maintenance.
Openbravo may be required to execute emergency maintenance in order to protect the security, performance, availability, or stability of the production environment. Emergency maintenance may include core system maintenance as required. Openbravo works to minimize the use of emergency maintenance and will work to provide 24 hours prior notice of any emergency maintenance requiring a service interruption.
Major Maintenance Changes
To help ensure continuous stability, availability, security and performance of the cloud services, Openbravo reserves the right to perform major changes to its hosting infrastructure, system software and supporting application software under its control, no more than twice per calendar year. Each such change event is considered scheduled maintenance and may cause the cloud services to be unavailable for up to 24 hours. Each such change event is targeted to occur at the same time as the scheduled maintenance period. Openbravo will work to provide up to 60 days prior notice of the anticipated unavailability.
Data Center Migrations
Openbravo may migrate Customer services between production data centers of the hosing provider in the same data center region in order to recover Customer services or in the case of disaster recovery. For all other data center migrations, Openbravo will work to provide a minimum of 30 days notice to Customer.
The Customer must always keep installation inside the acceptable version range of Openbravo supported versions. This means to be always in the latest CS (Confirmed Stable) version minus 4 releases back or newer.
In most situations, maintenance will require us to disable access temporarily while we perform maintenance activities. Openbravo makes every effort to minimize downtime during such events.
Openbravo makes backups of production data nightly for Openbravo's sole use to minimize data loss in the event of a disaster.
Database backups are stored at the primary site used to provide the Openbravo Cloud services, as well as at an alternate location for redundancy purposes. A backup is retained for a period of at least 30 days (1 copy per day) after the date that the backup is made. Openbravo typically does restore Customer data on behalf of the Customer. However, on an exceptional basis and subject to written approval and additional fees, Openbravo may assist the Customer to restore data, which the Customer may have lost as a result of their own actions.
On top of that periodic backup, continuous archiving of the database Write Ahead Log (WAL) assures that on recovery the database transactional data can be recovered up to very close to the point of failure and not only up to the point of the last regular backup. For these backups only the latest is kept as they are designed to just go back to the latest system status.
Disaster recovery operations apply to the physical loss of infrastructure of facilities used for the cloud Offering. Openbravo provides for the recovery and reconstitution of its production cloud services to the most recent available state following a disaster. To achieve that Openbravo has established alternate processing sites to accommodate full operating capability in the event of loss of service at a primary facility. Openbravo maintains a Disaster Recovery Plan that describes recovery procedures that is tested yearly.
In the event of activating the Disaster Recovery Plan, Openbravo will work to ensure a RTO (Recovery Time Objective) of 12 hours from the declaration of the disaster and a RPO (Recovery Point Objective) of 1 hour from the occurrence of a disaster. Complete definition of these objectives can be read in the Service Terms.
This Policy and the corresponding Disaster Recovery Plan is reviewed annually. The Plan is revised during the review process to incorporate problem resolutions and process improvements.
Openbravo uses a variety of software tools to monitor the availability and performance of the Customer's production environment and the underlying infrastructure.
Monitored components include CPU, memory usage, disk space usage, disk activity, network activity, database metrics and application performance information. Openbravo operations staff attend to any automated warnings and alerts associated with deviations of Openbravo defined monitoring thresholds and follow standard procedures to investigate and resolve underlying issues.
Yes. Note however that the Openbravo Cloud requires an Enterprise edition and your system to be at a minimum release level, which is RR15Q2 for the Commerce Suite or PR15Q2 for the Business Suite. In case you are in an older version, an upgrade will first be required before moving to the Openbravo Commerce Cloud or Openbravo Business Cloud. Contact your Openbravo Partner for further details about this process.
Yes, if you ever decide to take your data back to your on premise solution, Openbravo and your Partner will work with your company to hand over the database backups and ensure the process is as seamless as possible.
By moving your Openbravo solution to the cloud, you have access to all the business features of Openbravo as you would with a traditional on premise implementation. In order to guarantee the assured levels of service only a few restrictions are applied: installation of additional software on a server outside of Openbravo or a database change are not allowed, and the application domain name cannot be chosen.
Third-party developed modules will work in the same way as they do in an On Premise environment. The only exception to this is in the case that a module requires to install additional software in the same Openbravo server, which is not allowed.
Yes, web service access is enabled. There is no extra cost for that.
Yes. Openbravo Cloud provides you with a dedicated Openbravo instance where you can customize your Openbravo solution in the same way as any on premise instance. The only restriction applies to the capacity to install extra software outside of Openbravo.
With the Openbravo Cloud you pay a yearly subscription for the deployed cloud infrastructure in AWS and related cloud services.
Openbravo Cloud fees do not include the required fees for the Openbravo Commerce Suite or Openbravo Business Suite subscription that will be priced separately based on the number of subscribed concurrent users, POS terminals and additional functionality.
Yes, one year. You must acquire a yearly subscription with in advance yearly billing.
Openbravo Cloud subscription is not based on concurrent users and POS terminals but on the deployed cloud infrastructure and services. It is the Openbravo Commercial Edition sold in combination with the Openbravo Cloud that determines the minimum number of concurrent users and POS terminals.
No, you can have as many concurrent users and terminals as you want. The elastic architecture allows to scale to significant numbers.
Yes, licensing for both is included in the pricing. Openbravo Cloud comes with Ubuntu LTS Server and PostgreSQL database.
Yes. You can cancel your Openbravo Commerce Cloud or Openbravo Business Cloud subscription at any time within your subscription period. We require a minimum of 30 days written notice prior to termination or change in any aspect of your Openbravo Commerce Cloud or Openbravo Business Cloud subscription.
For a period of up to 30 days from notice of termination or expiration we will provide you with access to your data. Openbravo has no obligation to retain the data for Customer purposes after this 30-day post termination period. All Openbravo Cloud environments (production, reporting, test) adhere to the same service termination policy.
All your data is exportable during normal operation by yourself. This includes all database data, all attached documents as well as the application source code. Your Partner can provide assistance to access your data if required.