Skip to content

Terms & Conditions

These Terms & Conditions govern your access to and use of DevOpsCentral services.

1. Who These Terms Apply To

These terms apply to customers, users, and organizations that access, trial, order, or use DevOpsCentral services.

DevOpsCentral services may be used by both business customers and individual consumers. Some services, responsibilities, or commercial arrangements may differ depending on whether you use a standard Self-Managed service, a Co-Managed service, or a program such as Launchpad 90.

2. Definitions

For the purposes of these terms:

  • DevOps Central means DevOps Central SRL, the provider of the services.
  • Services means the cloud, infrastructure, Kubernetes, CI/CD, DevOps, onboarding, support, and related services made available by DevOps Central.
  • Customer means the person or organization that creates an account, places an order, enters into an agreement, or uses the services.
  • Consumer means a natural person acting for purposes outside that person's trade, business, craft, or profession.
  • Business Customer means a customer acting for professional purposes. Customer classification depends on the capacity in which the person acts and is not determined solely by company fields in an account or order form.
  • Self-Managed services means services where the customer is responsible for workloads, configuration, backups, and operations inside its own environment unless a separate written agreement states otherwise.
  • Co-Managed services means services where DevOps Central performs additional operational work to the extent defined in the selected plan, proposal, order, or separate written agreement.
  • Launchpad 90 means the specific DevOps Central program described in these terms and any related service description.
  • Separate written agreement means a signed contract, order, proposal, or other written document that expressly supplements or overrides parts of these public terms for a specific service scope.

3. Contracting Party

Unless a separate written agreement states otherwise, the contracting party is:

  • DevOps Central SRL
  • CUI: 43662656
  • Trade register number: J2021001763400
  • Registered address: Sos. Gheorghe Ionescu Sisesti 146-156 Bl. E Et. 4 Ap. 17, Sector 1, Bucuresti, Cod 013823
  • Contact email: legal@devopscentral.eu
  • Phone: +40 744 543 476

Romanian law applies to these terms. Unless a separate written agreement states otherwise, disputes are handled by the competent courts determined under applicable law.

4. Services Covered

These terms cover DevOpsCentral's public cloud and related services, including:

  • OpenStack-based infrastructure services
  • Kubernetes and Rancher-related services
  • CI/CD and DevOps services
  • Self-Managed Cloud
  • Co-Managed DevOps services
  • Launchpad 90
  • Related onboarding, support, and operational services

The services are digital and cloud services. Physical-goods shipping and returns do not apply, without limiting any statutory consumer rights.

Specific commercial or technical details may also be defined in an order, proposal, service description, pricing page, or separate written agreement.

If there is a conflict between these public terms and a separate written agreement for the covered service, that agreement takes precedence.

5. Account Provisioning, Acceptance, and Resource Use

5.1 Account Provisioning

Account registration, email verification, automated account provisioning, login, and access to Voyager, Horizon, and Skyline are non-chargeable. Automated provisioning normally completes within 1 to 3 minutes, depending on platform load, and runs continuously rather than as business-day processing.

The Consumer provisions in these terms apply when the relevant service is used by a Consumer; they do not necessarily apply to every service or Customer.

5.2 Acceptance and Contract Formation

For Self-Managed pay-as-you-go services, the master pay-as-you-go contract is formed when you accept these terms during PayU card enrollment and successfully save a valid payment method. The card-enrollment flow informs you that saving the card accepts these Terms.

For a Consumer, this contract-formation event starts the statutory 14-day withdrawal period. DevOps Central records the applicable Terms version, acceptance timestamp, and account or contract ID as electronic evidence of acceptance.

5.3 Payment Method Enrollment

Payment methods are enrolled and verified through PayU. Card enrollment or verification is not an upfront payment for resources.

5.4 Resource Allocation and Chargeable Usage

A customer request is chargeable only when the requested resource operation succeeds and billable capacity is provisioned or allocated. A rejected or unsuccessful request does not create a charge unless capacity was actually allocated and metered.

The applicable technical and commercial parameters, including available rates, may be shown in Voyager, on a pricing page, by a public calculator, in a proposal, service description, or separate written agreement.

5.5 Consumer Immediate Service

For a Consumer using Self-Managed pay-as-you-go cloud services, enabling cloud resources during the withdrawal period requires a separate, clearly identified affirmative request for service to begin. Acceptance of these terms and payment-method enrollment do not by themselves make that request.

6. Accounts and Access

6.1 Account Information

You must provide accurate information when creating and maintaining an account. You are responsible for keeping your account details up to date.

6.2 Credentials and Access Control

You are responsible for the confidentiality of your login credentials and for activity performed through your account or authorized users.

6.3 Authorized Use

You may use the services only for lawful purposes and in line with these terms, your selected service model, and any separate written agreement.

7. Acceptable Use

You must not use the services to:

  • violate applicable law or third-party rights
  • distribute malware, malicious code, or unauthorized access tools
  • send spam or operate abusive messaging activity
  • attack, scan, disrupt, or overload infrastructure without authorization
  • bypass security controls or attempt unauthorized access
  • use the platform in a way that creates material risk for other customers or for the stability of the service

DevOps Central may restrict, suspend, or terminate access where needed to protect the platform, customers, or legal compliance.

8. Service Models and Responsibility Split

8.1 Self-Managed Cloud

For Self-Managed services, you are responsible for everything inside your own OpenStack project or tenant, including:

  • virtual machines
  • applications
  • databases
  • operating system administration
  • workload security configuration
  • data protection and backups

DevOps Central is responsible for the underlying platform layer, not for the content or configuration inside your tenant.

8.2 Co-Managed DevOps

For Co-Managed services, the exact operational scope depends on the selected plan, proposal, order, or separate written agreement.

DevOps Central configures or monitors backups only when that responsibility is specifically requested by you or explicitly included in the agreed Co-Managed scope.

8.3 Launchpad 90

Launchpad 90 is available for both B2B and B2C customers.

At the end of the 90-day period, you must notify DevOps Central if you want to continue. If you do not notify DevOps Central within 15 days after the end of the 90-day period, DevOps Central may delete the related resources and close or block the account.

9. Billing and Payment

9.1 Usage-Based Monthly Billing

Regular paid services are usage-based and billed on a pay-as-you-go postpaid model. Usage is metered during each calendar month and invoiced monthly in arrears. There is no fixed order total or upfront payment for resources.

The final invoice is based on recorded usage and the applicable unit rates.

9.2 Consumer Initial Quota and Withdrawal-Period Uplifts

Self-Managed pay-as-you-go cloud services may begin with a limited initial quota. The available quota is shown in the relevant account or service flow and is not a statement that the service is free.

Where a Consumer validly withdraws within the 14-day withdrawal period, DevOps Central contractually waives charges for consumption within that Consumer's initial quota. This policy does not limit statutory rights and does not apply to usage or charges that are lawfully due outside that policy.

A Consumer may submit a request to increase the quota during the withdrawal period. The request remains pending and is neither approved nor applied until that period has expired. A valid withdrawal cancels any pending quota-increase request.

If the Consumer does not withdraw, regular pay-as-you-go billing applies under this contract.

9.3 Rates, Estimates, and VAT

Rates are displayed in Voyager and may also be shown by a public calculator. Calculator and forecast results are estimates; the final invoice is based on recorded usage and the applicable unit rates. Prices are shown without VAT unless stated otherwise. VAT is added where required by applicable law.

9.4 Payment Method and Verification

Payments are processed through PayU GPO. DevOps Central does not store card data or payment instrument details. DevOps Central may retain the payment-method verification status as part of its electronic service and billing records.

9.5 Payment Due Date

Invoices are due within 15 days after invoice issuance, unless a separate written agreement states otherwise.

10. Late Payment and Non-Payment

If an invoice is not paid on time, DevOps Central may apply the following process:

  1. During days 16 to 30 after invoice issuance, DevOps Central may notify you and request payment.

  2. At 30 days after invoice issuance, DevOps Central may stop existing machines and restrict access to new resources.

  3. DevOps Central may keep the affected resources for an additional 30 days so that recovery or migration remains possible.

  4. At 60 days after invoice issuance, DevOps Central may delete the affected resources.

If the process reaches resource deletion, DevOps Central may cancel the unpaid invoice and end the commercial relationship with that customer.

If non-payment reaches the resource deletion stage, recovery may no longer be possible. Keep your own backups and respond to payment notices promptly.

11. Support, Availability, and Service Levels

11.1 Service-Level Position

Support response times, availability expectations, and service-level descriptions are target-based unless a separate written agreement states otherwise.

Unless separately agreed in writing, documentation, support language, and pricing pages do not create a custom SLA, guaranteed uptime percentage, automatic service credit, or other guaranteed remedy beyond what is expressly agreed.

11.2 Service Boundary

DevOps Central is responsible for the underlying platform layer used to deliver the agreed service, consistent with the selected service model.

For Self-Managed services, DevOps Central is not responsible for the internal health, configuration, security, backup, or recovery of customer workloads running inside the customer's own project or tenant.

For Co-Managed services, workload-level responsibilities apply only to the extent specifically included in the selected plan, proposal, order, or separate written agreement.

11.3 Maintenance and Operational Changes

DevOps Central may perform planned maintenance, emergency maintenance, security-related interventions, and operational changes needed to protect platform stability, customer security, or legal compliance.

Where reasonably possible, DevOps Central will try to provide notice for planned maintenance. Emergency work may be performed without advance notice where necessary.

11.4 Exclusions

Service-level targets do not apply to issues caused by factors outside DevOps Central's reasonable control or outside the agreed service boundary, including:

  • customer-side misconfiguration
  • customer-managed credentials or access issues
  • unsupported changes made by the customer
  • customer workload failures in Self-Managed environments
  • third-party failures outside DevOps Central's control
  • emergency security actions or compliance-driven interventions

12. Consumer Withdrawal, Customer Exit, and Service Suspension

12.1 Consumer Withdrawal Procedure

A Consumer may withdraw from the master pay-as-you-go contract within the statutory 14-day withdrawal period by:

  • using the online Withdraw and close account facility;
  • emailing legal@devopscentral.eu; or
  • sending another unequivocal statement of the decision to withdraw.

Use of the model form below is optional. A withdrawal sent before the end of the withdrawal period is timely.

DevOps Central confirms receipt of a withdrawal on a durable medium, including the declaration content, account or contract ID, and the date and time received. The withdrawal process closes the account and cancels pending quota-increase requests. Cloud resources stop and deletion follows the account closure process. Before confirming withdrawal, export and back up any data you need: deletion is irreversible.

DevOps Central returns payments received without unjustified delay and no later than 14 days after receiving a valid withdrawal, using the original payment method unless otherwise agreed and subject only to amounts lawfully due. The contractual waiver in section 9.2 applies to initial-quota consumption on a valid withdrawal.

12.2 Model Withdrawal Form

To: DevOps Central SRL, Sos. Gheorghe Ionescu Sisesti 146-156 Bl. E Et. 4 Ap. 17, Sector 1, Bucuresti, Cod 013823, legal@devopscentral.eu

I hereby give notice that I withdraw from my pay-as-you-go contract for DevOpsCentral services.

  • Account or contract ID:
  • Contract formation date:
  • Consumer name:
  • Consumer address:
  • Date:
  • Signature (only if this form is submitted on paper):

12.3 Regular Account Closure

Regular paid services do not require a special cancellation workflow. You continue to pay for metered usage and billable allocations.

To stop future charges, you must delete, release, or deallocate your resources and billable allocations. Stopping a resource may leave storage, addresses, snapshots, or other billable allocations in place.

Regular account closure outside the Consumer withdrawal procedure is distinct from withdrawal and does not change amounts due for service usage.

12.4 Suspension by DevOps Central

DevOps Central may suspend or restrict access where reasonably necessary for:

  • non-payment
  • suspected abuse
  • security risk
  • unlawful use
  • platform protection
  • compliance with legal obligations

Where reasonably possible, DevOps Central will try to notify you before or during such action.

13. Data, Backups, and Customer Content

You retain responsibility for your workloads, data, and content unless a separate written agreement states otherwise.

For Self-Managed services, you are responsible for backup, export, recovery, and application-level resilience inside your environment.

For Co-Managed services, backup or recovery responsibilities apply only where they are explicitly included in the agreed service scope.

Following account closure or withdrawal, DevOps Central may retain electronic records of Terms acceptance, card-verification status, resource operations and outcomes, applicable rates, metered usage, invoices and payment notices, withdrawal requests, and relevant manual reviews or failures, together with billing, payment, security, fraud, dispute, and accounting records. Such records are retained only as needed for applicable data-protection, accounting, legal, security, fraud-prevention, dispute, or claims purposes.

14. Intellectual Property and Confidentiality

You retain ownership of your data, applications, and other customer-provided content.

DevOps Central retains ownership of its platform, documentation, service materials, trademarks, branding, and pre-existing intellectual property.

Both parties must treat non-public commercial, technical, and operational information received from the other party with reasonable confidentiality, unless disclosure is required by law or by a separate agreement.

15. Warranties, Liability, and Indemnification

15.1 "As Is" Services

Unless a separate written agreement states otherwise, DevOps Central provides the services on a commercially reasonable basis, "as is" and "as available," without implied warranties of merchantability or fitness for a particular purpose.

15.2 Limitation of Liability

Nothing in these terms excludes rights or liabilities that cannot be excluded or limited under applicable law.

To the maximum extent permitted by law, DevOps Central is not liable for indirect, incidental, special, consequential, or punitive damages, including loss of profits, revenue, or data.

DevOps Central's total cumulative liability for any claims relating to the services is limited to the amount the customer paid DevOps Central for the affected service during the 12 months immediately preceding the event.

DevOps Central is not responsible for loss caused by customer-side configuration, customer-managed credentials, unsupported changes, or failures to maintain appropriate backups.

15.3 Indemnification

You agree to indemnify and hold harmless DevOps Central from any third-party claims, damages, or legal fees arising from your violation of these terms, your workloads, or your data.

16. Force Majeure

Neither party will be liable for performance delays or failures caused by events outside their reasonable control, such as natural disasters, acts of war, terrorism, labor disputes, governmental actions, or regional internet and utility outages. This does not excuse the customer's obligation to pay for services delivered.

17. Changes to These Terms

DevOps Central may update these terms from time to time to reflect legal, operational, or commercial changes.

Updated versions will be published in the legal section of this documentation site or otherwise made available through the relevant service or ordering flow.

Your continued use of the services after an updated version becomes effective means the updated terms apply, except where applicable law requires a different treatment or where a separate written agreement already governs the same issue.

The legal framework for DevOpsCentral services also includes the following supporting documents, where applicable:

These documents address different topics and apply together where relevant.

Unless a separate written agreement states otherwise:

  • these Terms & Conditions govern the general commercial and service relationship
  • the Privacy Policy governs how DevOps Central handles personal data in its own controller role
  • the DPA governs processor-role topics relating to customer workload data where applicable

19. Consumer Complaints

Consumers may submit complaints by email to legal@devopscentral.eu or by post to the registered address above. Phone is also a contact channel, but complaints do not need to be submitted by phone. Please include your name, account or contract ID where available, relevant dates, a description of the issue, supporting information, and the resolution you request.

DevOps Central will acknowledge receipt within 2 business days and provide a substantive written response within 30 calendar days. If more time is reasonably needed, DevOps Central will, within that 30-day period, explain the status, reason, next steps, and expected response date.

Technical or support requests should be sent to support@devopscentral.eu. Privacy or GDPR requests should be sent to privacy@devopscentral.eu and handled under the Privacy Policy. A message may be handled according to its substance.

This policy does not limit statutory rights or access to the ANPC complaint portal, an applicable SAL entity, competent authorities, or courts.

20. Contact

For legal notices, withdrawals, refunds, complaints, or questions about these terms, contact legal@devopscentral.eu.

For privacy or GDPR requests, contact privacy@devopscentral.eu and see the Privacy Policy and the Data Processing Agreement (DPA) page.

For general inquiries, contact contact@devopscentral.eu.