Terms of Use

These Terms of Use govern access to and use of the BedrockOps website at bedrockops.io and the BedrockOps service.

1. Acceptance of these terms

By accessing or using the BedrockOps website (bedrockops.io) or the BedrockOps service, you enter into a binding agreement with BedrockOps on these terms. A Customer that does not agree to these terms must not use the Service.

2. Definitions

• “BedrockOps” — the provider of the Service.
• “Service” — the BedrockOps operational and incident-intelligence software-as-a-service for Amazon Bedrock, including the dashboard at app.bedrockops.io.
• “Customer” — the company or other legal entity that registers for or subscribes to the Service.
• “User” — an individual who accesses the Service on a Customer’s behalf.
• “AWS” — Amazon Web Services, the third-party cloud provider that operates Amazon Bedrock.
• “AWS Marketplace” — the AWS procurement and billing channel through which the Service is sold.
• “DPA” — the BedrockOps Data Processing Agreement referenced in clause 8.
• “Privacy Policy” — the BedrockOps Privacy Policy.

3. The Service

BedrockOps is the operational and incident-intelligence layer for Amazon Bedrock production systems. The Service reads the Customer’s Amazon Bedrock operational telemetry through a read-only cross-account IAM role that the Customer provisions in its own AWS account, and interprets that telemetry — explaining quota waste, throttling root causes, and Knowledge Base failures.

• Read-only by default. The cross-account role the Service uses is read-only. BedrockOps reads, interprets, and recommends.
• No customer-side runtime, no proxy. BedrockOps does not sit in the request path between the Customer’s application and Amazon Bedrock, never proxies a Bedrock call, and deploys no runtime inside the Customer’s account.
• Amazon Bedrock only in V1. The Service covers Amazon Bedrock; it is not a multi-LLM-provider product.

The Service provides decision support: it ranks probable causes and surfaces findings for human operators to review and act on (see clause 10).

4. Accounts and eligibility

Each User represents that they are authorised to bind the Customer entity on whose behalf they use the Service, and that they have the legal capacity to enter into a binding agreement. The Customer must provide accurate, current, and complete registration and account information and keep it up to date; how that information is handled is described in the Privacy Policy. Users are responsible for safeguarding their credentials and for the activity under their accounts.

5. Acceptable use

When using the Service, the Customer and its Users must not:

• abuse, disrupt, or interfere with the Service or its infrastructure;
• attempt to circumvent security controls, rate limits, spend caps, or plan entitlements;
• reverse engineer, decompile, or otherwise attempt to derive the source code of the Service, except to the extent such a restriction is prohibited by applicable law;
• attempt to access another tenant’s data or another Customer’s account without authorisation;
• use the Service in any unlawful way; or
• use the Service in a way that violates the Customer’s own agreements with AWS, including the AWS Customer Agreement and the applicable AWS Marketplace terms.

BedrockOps may investigate suspected violations of this clause and may act on them, including as described in clause 14 (Suspension and termination).

6. Subscription, trial, and billing

All billing runs exclusively through AWS Marketplace — there is no direct web checkout — and BedrockOps never stores payment details.

The Service offers a 7-day free trial that requires no payment card. At the end of the trial, the account transitions to read-only access until the Customer subscribes — never an auto-upgrade.

Paid plans bill a fixed monthly plan plus usage-based overage: +$49 per additional AWS account per month and +$10 per additional Knowledge Base per month. The Customer may set a monthly spend cap; at the cap, protected mode pauses high-volume ingestion while dashboards, incident history, and alerts stay operational.

The AWS Marketplace terms govern the payment relationship between the Customer and AWS. Refunds and cancellations follow the applicable AWS Marketplace and plan terms.

7. Customer responsibilities and AWS costs

The Customer is responsible for:

• deploying and maintaining the read-only cross-account IAM role in its AWS account (provisioned through the Quick-Create CloudFormation link), and the accuracy of the AWS account information it provides;
• its own AWS charges arising from the Service’s read-only API calls, which are signed with the Customer’s role and land on the Customer’s AWS bill. The dominant line is CloudWatch Logs Insights scans — approximately $3–8 per month, depending on log volume and configuration. This range is indicative, not a guarantee.

BedrockOps provides cost-control levers — collector mode toggles and activity-tier cadence — but the Customer’s AWS bill remains the Customer’s responsibility.

8. Customer data, privacy, and GDPR

The Customer retains ownership of its data. BedrockOps’s processing of personal data is governed by the Privacy Policy and the Data Processing Agreement (DPA), which is available to customers on request.

The Service is single-region and EU-hosted for GDPR data residency. Customer data is never aggregated across tenants.

BedrockOps is fully GDPR-compliant. The GDPR rights you can exercise, and how, are described in the Privacy Policy.

9. Intellectual property

BedrockOps owns the platform, the software, and all related intellectual property. Subject to these terms, BedrockOps grants the Customer a limited, non-exclusive, non-transferable right to use the Service during the subscription term. The Customer keeps ownership of its data, as described in clause 8. No rights are granted beyond those expressly stated in these terms.

10. Warranties and disclaimers

BedrockOps findings are decision support for human operators: the Service ranks probable causes and surfaces findings for people to review. They are not a guarantee of any outcome, and the Service is not a substitute for the Customer’s own security, compliance, and operational obligations.

These terms make no specific availability commitment. Any service-level or availability commitment offered for a particular plan is defined in that plan’s terms.

11. Limitation of liability

Some jurisdictions do not allow certain exclusions or limitations of liability, so parts of this clause may not apply to a given Customer. In that case, this clause applies to the maximum extent permitted, and the rest of it stays in effect (see clause 19, Severability).

12. Indemnification

The Customer will indemnify and hold harmless BedrockOps against third-party claims arising from the Customer’s unlawful use of the Service, the Customer’s breach of these terms, or the Customer’s data or content — in each case to the extent permitted by applicable law, and limited to claims attributable to the Customer’s own acts or omissions.

13. Changes to the Service

BedrockOps may modify, improve, or discontinue features of the Service, and will use reasonable efforts to communicate material changes. The V1 Service is described in these terms as it exists today — read-only, Amazon Bedrock only. Roadmap items are not promised as available.

14. Suspension and termination

BedrockOps may suspend or terminate access to the Service for breach of these terms, for non-payment (handled through AWS Marketplace), or where reasonably necessary to protect the Service or other customers. The Customer may stop using the Service at any time and may cancel its subscription per the applicable AWS Marketplace and plan terms. On termination, the Customer’s data is handled as described in the Privacy Policy and the DPA — including the GDPR data-deletion workflow described there.

15. Survival

Clauses that by their nature should survive termination do survive — including clause 9 (Intellectual property), clause 10 (Warranties and disclaimers), clause 11 (Limitation of liability), clause 12 (Indemnification), and clause 16 (Governing law and dispute resolution).

16. Governing law and dispute resolution

These terms are governed by applicable law, and any dispute that cannot be resolved informally will be brought before the courts of competent jurisdiction. Nothing in this clause affects any mandatory rights you have under the laws that apply to you.

17. Notices

Legal notices to BedrockOps must be given in writing. Notices to the Customer are given at the email address registered on the Customer’s account.

18. Changes to these terms

Material changes to these terms are published on this page and, where required, notified to customers. Continued use of the Service after a change takes effect constitutes acceptance of the updated terms, to the extent permitted by applicable law.

19. Entire agreement and miscellaneous

These terms — together with the Privacy Policy and the DPA — are the entire agreement between BedrockOps and the Customer for the Service.

• Severability. If any provision of these terms is held unenforceable, that provision applies to the maximum extent permitted, and the remaining provisions stay in full effect.
• No waiver. A failure to enforce a provision of these terms is not a waiver of it.
• Assignment. The Customer may not assign these terms without BedrockOps’s prior written consent; BedrockOps may assign them to a successor in a merger, acquisition, or sale of substantially all assets.