Ramphast

Terms of Service

Version 1.0 — in force from 30 October 2026. These Terms are also published in Spanish; if the two differ, the Spanish version prevails.

These Terms are entered into between Felix Daniel Coca Calvimontes, trading as Bastion Solutions, of Santa Cruz de la Sierra, Bolivia (the "Provider"), owner of the Ramphast service, and the legal entity or business that accepts them when it opens its account or that is named in the Service Order (the "Partner"). Whoever accepts them on the Partner's behalf represents that they have the authority to bind it.

1. Definitions

2. Businesses only

2.1. The Service is provided only to legal entities or businesses that use it in the course of their trade, never to consumers. The Partner represents that it contracts in that capacity.

3. The Service and its scope

3.1. For the term of these Terms, the Provider grants the Partner a non-exclusive, non-transferable, non-sublicensable right to use the Service to manage Odoo instances on its Servers and to provide services to its Clients, including under the Partner's own brand.

3.2. The Provider also grants a licence, on the same conditions and only for the term, to install and run the Agent on the Servers. The Agent is delivered only as a compiled program signed by the Provider, without its source code. The Partner may not decompile, modify or redistribute it, or use it outside the Service, except as applicable law or clause 14.3 allows.

3.3. What the Service does. On the Servers, it creates, updates, copies, restores and deletes Odoo Community instances, each with its production, staging and dev environments; staging and dev stop when nobody is using them and start on the next visit. It publishes their addresses, including custom domains, through the Partner's Cloudflare account. It sends and receives those instances' email through the Service's mail relay and the email provider the Partner configures. It stores backups in the storage the Partner configures and checks that they can be restored. It deploys code from the GitHub repositories the Partner connects. It gives Clients a portal to view their service, choose a plan, bring a backup and open support tickets with the Partner, and to pay when the Service allows charging Clients. Some of these features depend on the Plan (clause 3.10).

3.4. What the Service does not do. It does not host Clients' instances on the Provider's infrastructure. It does not provide the Servers or their operating system, network, power or connectivity, nor the Third-Party Accounts. It is not an independent backup service: Clients' backups live where the Partner configures them and never in the Provider's storage, and the Partner is responsible for keeping its Clients' backups. Once the Partner has configured where they are stored, the Service encrypts its Clients' backups and checks that they can be restored.

3.5. If the panel goes down. Odoo instances keep serving from the Servers, with their databases, scheduled tasks, addresses and certificates. While the panel does not respond, the following stop:

  1. Operations ordered from the panel (create, update, restore) and deployments from GitHub;
  2. Scheduled backups, their verification and their retention, which resume when the panel is back;
  3. The instances' email: outgoing mail stays in Odoo's queue, which retries it, and incoming mail is not delivered until the panel is back;
  4. Starting a stopped staging or dev environment;
  5. The Clients' portal and the terminal; and
  6. The private network between Servers for a Server that restarts, until the panel is back.

3.6. Sign-up. The Partner may sign up on its own from the Service's website, when the Provider has sign-up open. The account exists from the moment its email address is confirmed, and the Trial runs from then. Whoever creates it accepts these Terms and the Data Processing Agreement on the Partner's behalf when choosing their password; until then the panel cannot be used.

3.7. Trial. A Partner that signs up gets a free Trial, with no card, with the length, Production Instances, features and Servers the Service states at sign-up (currently 14 days, up to 2 Production Instances and what the Plan named by the Service includes). During the Trial, creating a Production Instance beyond that number is refused. The Provider may change those conditions; the length of a Trial in progress does not change.

3.8. The Trial ends when the Partner chooses a Plan, or on its last day. If it ends without a Plan, the panel becomes read-only: instances, their scheduled backups and the Clients' portal keep working, deployments from GitHub are ignored, and choosing a Plan lifts it. Three days before the end, the Service gives notice by email.

3.9. If the Partner has not chosen a Plan thirty (30) days after the Trial ends, the account ends under clause 16.4. The notice of the end of the Trial states that date.

3.10. What depends on the Plan. Major Odoo upgrades, the web terminal, external database access, sending logs to a destination of the Partner's and charging Clients are included according to the Plan. Everything else in clause 3.3 is included in every Plan.

4. Each party's responsibilities

4.1. The Partner is responsible for:

  1. The hardware, operating system, network, firewall and availability of the Servers, and the invoices and contracts with its Server provider;
  2. Contracting, paying for and complying with the terms of the Third-Party Accounts, and giving each one the least permission the Service needs;
  3. Configuring backup storage and checking that the backups work for it;
  4. Licences for Odoo Enterprise and for third-party modules;
  5. The modules and code chosen by the Partner or its Client;
  6. The contract, invoicing and support for its Clients;
  7. Complying with data protection law towards its Clients, as controller; and
  8. Scheduling the Agent's updates on its Servers.

4.2. The Provider is responsible for:

  1. Running, securing and backing up the panel;
  2. Storing the Third-Party Accounts' credentials encrypted;
  3. Publishing signed Updates of the Agent; and
  4. Supporting the Partner under clause 8.

5. The Service's access to the Servers

5.1. The Partner authorises the Service to run on its Servers, through the Agent and with administrator privileges, the operations needed to provide it. The Agent is what opens the connection to the panel: the panel does not log in to the Servers over SSH or connect directly to their databases. The Service stores encrypted the administrator credentials of the databases it creates on the Servers.

5.2. The Service runs the operations ordered by the Partner's staff or by its Clients from the portal, and the recurring tasks the Service performs for the Partner (backups, verifications, counts, checks). Each operation records who ordered it and when, and the audit log keeps every action of the Partner's staff with its user, date and IP address. That log is the record of who did what, and it is kept for the period the Provider sets.

5.3. The Provider does not access the Servers or the Clients' databases on its own initiative, except to (a) handle a support request from the Partner, (b) contain a security incident in progress or (c) comply with an order from a competent authority. From its own console, the Provider cannot act as the Partner's staff, but it can see the account's data and usage, reset a person's two-step verification, download the export of clause 16.3, deactivate the account and move it to another region. It does so only for those same reasons, on termination or at the Partner's request. Each of those actions and each access is recorded, and the Provider reports them to the Partner unless the law forbids it.

5.4. Agent Updates. Agent Updates are signed by the Provider and the Partner decides when they are installed. The Provider may set a minimum version. A Server with an older Agent stops receiving new operations, but its instances keep working.

6. The Partner's obligations

6.1. To keep its Servers updated and secure, and not to disable the controls the Agent installs.

6.2. To safeguard its staff's credentials and to tell the Provider without delay of any unauthorised access it suspects. Every person who signs in to the panel or the portal uses a second verification (an authenticator app or a recovery code), unless the Provider disables it for the whole Service. The Partner's administrators can reset it for their staff and their Clients.

6.3. To make its Clients comply with the Acceptable Use Policy.

6.4. To hold the licences needed for all the software it runs on the Service, including third-party modules. If an instance uses Odoo Enterprise, the Partner warrants that its database has a current subscription with Odoo S.A., taken out by the Partner as an Odoo partner or by its Client, and that it obtained the Odoo Enterprise code lawfully. The Provider does not supply Odoo Enterprise's code, licences or subscriptions, nor does it check that they exist. Using Odoo Enterprise without the corresponding subscription is a material breach (clause 12.1 c).

6.5. Not to resell or assign the Service to another partner, not to use it to build a product that competes with it, not to circumvent the counting of Production Instances and not to attempt to access another partner's data.

7. Price and payment

7.1. The Partner pays for the Plan in advance for each period, monthly or yearly, in the currency of the published Plan (currently US dollars). When it pays online, the payment is processed by Paddle.com Market Ltd. ("Paddle"), which acts as reseller and merchant of record for the Service: Paddle takes the payment, issues the receipt, and calculates and collects the applicable taxes for the Partner's country, under its own buyer terms, which the Partner accepts when paying. The published price includes any applicable taxes: it is the total the Partner pays. A Partner the Provider charges in another way pays by the means set in the Service Order, and the Provider issues the corresponding invoice. Only a Partner administrator chooses, changes or pays for the Plan.

7.2. Exceeding the Plan's Production Instances never blocks the Service. The Service gives notice the first time it happens in a period and, one day before renewal, moves the subscription to the smallest public Plan of the same period that covers the period's maximum of Production Instances, which is the one charged from the renewal. If paid in another way, the Provider adjusts the Service Order. The Service never moves to a lower Plan on its own. The only thing a Plan limits by quantity is Servers, where it says so: registering one more is refused, and those already there remain.

7.3. The price may depend on the region of the country the Partner declares when signing up and when paying. Only the Provider changes the registered country, and the change applies to what is agreed from then on. Declaring another country to pay less is a breach.

7.4. A subscription keeps the price and what its Plan included when it was taken out, even if the published Plan changes, until the Partner changes Plan. The Provider may change the price of a subscription in progress with 60 days' notice; the change applies from the period after the notice, and the Partner may terminate without penalty before it applies.

7.5. When a payment fails, the Service gives notice by email with the date on which the panel will become read-only. If payment is not made within fifteen (15) days of that notice, the panel becomes read-only under clause 9 until it is paid. If Paddle cancels the subscription for non-payment, clause 7.7 applies.

7.6. Changing Plan. Moving to a higher Plan takes effect at once and the prorated difference is charged. Moving to a lower Plan also takes effect at once, only if the Production Instances the Partner uses fit in the new one, and the prorated difference is credited on the next invoice; a change that does not increase the Production Instances counts as moving down. The Plan cannot be changed while a payment is pending. A Plan with fewer features or Servers does not switch off anything already running: what the new Plan does not include can no longer be started.

7.7. Cancellation. The Partner may cancel its Plan at any time from Paddle's portal, reached from the panel ("Manage billing"). Cancellation takes effect at the end of the period already paid, with no new charges; from then the panel is read-only until it chooses a Plan again. Amounts already paid are refunded only in the cases of the Refund Policy.

8. Support and service level

8.1. The Provider supports the Partner at support@ramphast.io, on business days from 9:00 to 18:00, Bolivia time, with the response times of its Plan. Support for Clients is the Partner's, which handles it through the portal's tickets.

8.2. The Provider aims to keep the panel continuously available, but does not guarantee an availability percentage or offer a service level agreement (SLA). An interruption of the panel gives no right to credits; it gives a right to a refund only in the cases of the Refund Policy and of clause 13.1.

8.3. The Provider gives 48 hours' notice by email of scheduled maintenance that interrupts the panel.

9. Suspension

9.1. The Provider may make the Partner's panel read-only, or deactivate the account, if (a) a payment is more than fifteen (15) days overdue after notice, (b) there is a material breach of the Acceptable Use Policy or (c) it is necessary to contain a security risk to the Service or to other partners. Late payment leads to read-only; deactivating the account is reserved for (b) and (c).

9.2. No suspension stops or deletes the Clients' instances on the Servers. Read-only stops management from the panel; scheduled backups and the Clients' portal continue. Deactivating the account also closes the panel and the portal to the Partner's staff and its Clients, and stops recurring tasks except backups and their verification. Except in a security emergency, notice is given in advance, and the suspension is lifted as soon as its cause is gone.

10. Data

10.1. Partner Data belongs to the Partner. The Provider processes it only to provide the Service, as processor, under the Data Processing Agreement, which forms part of these Terms.

10.2. The Provider also keeps a daily snapshot of usage indicators of the Service (counts, durations and sizes; never content, names or addresses) to run and improve it, for three months at most, without selling or passing it to third parties, within the scope of annex B of that Agreement. The Partner's administrators see each snapshot as it is stored, under Administration → Telemetry. A figure that compares partners is computed only from five or more.

10.3. What passes through the Provider's infrastructure. Although the instances run on the Servers, the following pass through the Provider's infrastructure, and are processed under the Data Processing Agreement:

  1. the email the instances send and receive, in transit through the mail relay;
  2. the backups and modules the Partner or its Clients upload from the panel or the portal, until the Server downloads them, and for one week at most if unused;
  3. the encrypted backups of the panel itself, which contain Partner Data and are stored in the Provider's storage; and
  4. the instances' technical logs and errors, when the Service collects them to run them.

10.4. Clients' backups are encrypted with a key of each Server's own, which the Service derives from a key of the Provider's. The Partner receives them on termination (clause 16.3).

11. Liability

11.1. Cap. The Provider's total liability for any claim arising from these Terms, whether in contract or otherwise, does not exceed what the Partner paid for the Service in the twelve (12) months before the event giving rise to the claim.

11.2. Excluded damages. Neither party is liable for loss of profit, loss of business or customers, reputational damage, or indirect or consequential damages.

11.3. Data loss. The Provider is not liable for the loss of Clients' data that a backup in storage configured by the Partner would have prevented. The Partner is responsible for those backups existing, being kept and being restorable.

11.4. What is not the Provider's. The Provider is not liable for failures of the Servers, the Third-Party Accounts, Odoo or the modules chosen by the Partner or its Clients, nor for the operations the Partner or its Clients ordered.

11.5. Nothing in this clause limits liability for wilful misconduct or gross negligence, or the Partner's payment obligations.

12. Indemnity

12.1. The Partner will hold the Provider harmless against third-party claims, including from its Clients, arising from (a) the services the Partner provides to its Clients, (b) the data and content hosted in its instances, (c) the use of software without the necessary licence or (d) a breach of these Terms or of the Acceptable Use Policy.

12.2. The Provider will hold the Partner harmless against third-party claims alleging that the Service, used in accordance with these Terms, infringes intellectual property rights.

12.3. The party seeking indemnity gives notice without delay, leaves the defence to the other party and cooperates with it.

13. Warranties

13.1. The Provider warrants that the Service works substantially as its documentation describes. The only remedy is to fix the defect or, if that is not possible, to refund the price of the affected period.

13.2. Beyond that warranty, the Service is provided "as is". The Provider does not warrant that it will be uninterrupted or error-free.

14. Intellectual property and trademarks

14.1. The Provider keeps all rights in the Service and the Agent. The Partner's suggestions may be used freely.

14.2. "Odoo" is a trademark of Odoo S.A. The Provider is not affiliated with Odoo S.A. Odoo Community is obtained from its public source under LGPLv3. When the Service manages Odoo Enterprise, it does so with the code and subscription the Partner provides under clause 6.4.

14.3. The Service and the Agent include third-party components under their own licences; the notices of those in the Agent are delivered with it. Nothing in these Terms limits the rights those licences grant.

15. Confidentiality

Each party keeps confidential the other's non-public information it learns through the Service, uses it only for these Terms and protects it as its own. This obligation lasts for 3 years after termination.

16. Term and termination

16.1. These Terms apply from their acceptance and renew with each period of the Plan, until the Partner cancels under clause 7.7 or a party terminates under clause 16.2.

16.2. Either party may terminate if the other commits a material breach and does not remedy it within thirty (30) days of notice. The Partner may also ask the Provider to close its account at any time.

16.3. Exit. On termination:

  1. the Clients' instances stay on the Partner's Servers, which it owns;
  2. for thirty (30) days, which the Service announces by email, the Partner's administrators can download their data from the Service in a machine-readable format (JSON), without passwords, tokens or credentials, together with each Server's key and the tool to decrypt its backups without the panel; the same export can be downloaded at any time during the term;
  3. the Partner uninstalls the Agent from its Servers, which stop connecting to the panel; and
  4. once that period is over, the Provider deletes the Third-Party Accounts' credentials and the Partner Data, notifying it by email, except the records of payments, subscriptions and acceptance of these Terms, which it keeps as evidence and as required by law, and its telemetry under annex B of the Data Processing Agreement.

Backups the Partner wrote before each Server had its own key cannot be opened with what it receives under b); the Service points them out during the period so that they can be restored or made again.

16.4. A Trial without a Plan. When a Trial ends without the Partner choosing a Plan, the period of clause 16.3 b) runs from the last day of the Trial, and once it is over 16.3 d) applies. Choosing a Plan before it is over cancels it.

17. Changes to these Terms

17.1. The Provider may change these Terms with 30 days' notice through the panel and by email to the Partner's administrators. The new version states the date from which it applies, and from that date the Service asks for it to be accepted. If the Partner does not accept it, it may terminate without penalty before it applies.

17.2. Changes required by law or for security may apply earlier, with notice.

17.3. A new version of these Terms or of the Data Processing Agreement is accepted, for the Partner, by any of its administrators, together with any other pending documents. Until it is accepted, its administrators can only read and accept the documents, export the data and pay; the rest of its staff, its Clients and the instances keep working.

18. Governing law and disputes

18.1. These Terms are governed by the laws of the Plurinational State of Bolivia.

18.2. The parties will try in good faith to settle any dispute about these Terms for thirty (30) days from the moment one of them notifies the other. If they do not settle it within that period, it is submitted to the judges and courts of Santa Cruz de la Sierra, Bolivia.

19. General provisions

19.1. Neither party is liable for failures caused by force majeure or acts of God.

19.2. The Partner may not assign these Terms without the Provider's written consent. The Provider may assign them to whoever succeeds it in the Service, with notice.

19.3. If a clause is invalid, the rest remain in force.

19.4. These Terms, the Data Processing Agreement, the Acceptable Use Policy, the Refund Policy and the Service Order are the entire agreement between the parties. If they conflict, the Service Order prevails, then the Data Processing Agreement on data matters, and then these Terms.

19.5. Electronic acceptance of these Terms has the same validity as a handwritten signature. The Service keeps, without being able to change or delete them, the accepted version and the fingerprint of its text, the date, the user with their name and email at that moment, the IP address and the browser.

19.6. Notices: to the Provider at support@ramphast.io; to the Partner, at the email addresses of its administrators registered in the Service.