DevRails Terms of Service
Last Updated: June 9, 2026
Welcome to DevRails! Please read these Terms of Service ("Terms") carefully before using our platform.
1. About the Service and Operating Status
DevRails is a cloud usage monitoring, alerting, reporting, and optional guardrail automation tool for Google Cloud Platform (GCP) users. It is designed to help builders, indie hackers, and development teams detect and mitigate unexpected resource usage spikes.
- Operating Status: DevRails is currently operated by the founder of Coll-Con as a sole proprietorship. If Coll-Con later incorporates, reorganizes, or transfers operation of DevRails to a legal entity, references to "Coll-Con," "DevRails," "we," "us," or "our" will automatically refer to that successor entity.
- Early Access Phase: DevRails is currently in active development, early access, and pilot phases. Features, dashboard tools, polling loops, and supported integrations are subject to frequent updates and experimentation.
- Relationship to Google: DevRails is an independent software tool. Google is not an arbitrator, governing body, dispute-resolution authority, partner, sponsor, or legal authority for DevRails.
2. Eligibility
You must be legally able to enter into these Terms and use cloud infrastructure services in your jurisdiction. If you use DevRails on behalf of a team, company, school, or organization, you represent and warrant that you have the explicit authority to bind that entity to these Terms.
3. Service Scope and Supported Services Only
DevRails does not manage your cloud architecture or act as a financial insurer against your cloud bills. It reduces risk but does not eliminate it.
- Supported Coverage: DevRails only monitors explicitly supported GCP metrics and modules. Our active early-access scope targets:
- Cloud Run: To catch zombie traffic loops or high-volume execution surges.
- Cloud Functions: To detect runaway recursive execution chains.
- App Engine: To support basic legacy application monitoring.
- Pub/Sub: To avoid bill spikes stemming from unexpected high-velocity messaging volume.
- Exclusions: Coll-Con is not responsible for cloud costs generated by unsupported GCP services, unsupported metrics, GCP API changes, or billing bursts occurring outside our supported modules.
Critical Production Warning: DevRails is not intended to be blindly enabled on critical production workloads without thorough testing, review, and a complete understanding of the potential technical and operational consequences.
4. GCP Connection and Permissions
Users must connect their GCP environments to DevRails using our supported connection mechanisms, such as automated service accounts, APIs, OAuth, or Workload Identity Federation.
- Least Privilege: Users are responsible for reviewing requested permissions and should follow industry least-privilege practices when connecting environments.
- Configuration Failure: DevRails can only monitor or act within the exact permissions granted by the user. Missing, revoked, excessive, or misconfigured permissions may cause DevRails to fail entirely, behave unexpectedly, or execute guardrail actions in an unintended manner.
5. Data Polling and Service Availability
DevRails does not offer real-time infrastructure enforcement. We poll usage signals periodically, typically every 5 to 10 minutes, but intervals fluctuate based on system health and API boundaries. Massive cloud billing spikes can occur completely between polling windows.
We do not guarantee uninterrupted or error-free operations. DevRails availability or performance may become degraded or temporarily unavailable due to:
- Scheduled or emergency maintenance, deployment updates, or system upgrades.
- Unexpected software bugs, errors, or early-access instability.
- Third-party infrastructure provider outages, security incidents, or deployment errors.
- GCP API changes, response timeouts, or temporary cloud network failures.
6. Alert Mechanisms and Delivery Dependencies
When thresholds are breached, DevRails attempts to distribute alerts through channels like Email or Telegram. However, notifications can fail, bounce, or experience delays due to:
- Third-party network outages, messaging rate limits, or webhook transmission failures.
- Overzealous local email filters, spam folders, or incorrect user routing configurations.
Users are solely responsible for keeping their destination alert channels active, verified, and consistently monitored.
7. Soft Killswitch and Hard Killswitch Guardrails
If you choose to activate automated guardrail actions, you acknowledge and agree to the following operational behaviors:
- Soft Killswitch: May reduce selected configuration quotas, set designated API quotas to zero, limit baseline usage, or apply other reversible guardrail limits. This is intended to mitigate runaways but will cause localized service degradation and application errors.
- Hard Killswitch: May detach billing profiles, disable selected services, scale compute resources completely down to zero, or perform other highly disruptive actions depending on implementation. A hard killswitch requires your explicit opt-in and manual confirmation. This action will cause immediate application downtime and potential process data disruption.
Coll-Con is not responsible for any downtime, lost revenue, lost data, system interruption, or business impact caused by guardrail actions enabled by the user. Users must thoroughly test these behaviors before relying on them.
8. Pricing, Subscription, and Fair Use
A. Pricing
Our early access base plan is set at $1/month or $10/year, covering up to 5 monitored GCP projects. Additional blocks of 5 monitored environments are priced at an added +$1/month or +$10/year.
B. No Refunds
Unless required by applicable law or expressly stated otherwise, all payments made to DevRails are strictly non-refundable.
C. Fair Use
Our ultra-low price structure assumes normal, lightweight infrastructure monitoring. To preserve system stability, we may enforce caps on environment complexity, polling frequency, metric coverage, or notification volume. Abusive, excessive, or unusually massive cloud environments may result in plan changes, account throttling, or service limitations.
D. Payment Processing
Payments may be processed securely by third-party payment processors, including Stripe or other enterprise transaction providers we choose to utilize in the future.
E. Pricing and Service Changes
We reserve the right to change our pricing, plan structures, asset limits, or fair-use policies in the future. Where required or reasonable, we will provide you with clear advance notice before material pricing updates take effect.
9. Account Cancellation and Deletion
You may cancel active subscriptions, stop using the platform, request waitlist removal, or ask for account deletion at any time via your settings panel or by contacting support.
Upon an account closure request, we delete personal records in accordance with our system design. However, please note that some technical records may be securely retained where reasonably necessary for fraud prevention, legal compliance, billing verification, dispute resolution, or essential operational backups.
10. Acceptable Use
You agree that you will not use DevRails to engage in harmful, disruptive, or unlawful activities. Specifically, you must not:
- Attack, probe, or attempt to overload the DevRails application or infrastructure.
- Connect GCP environments or billing projects that you do not legally own or manage.
- Attempt unauthorized access to other user accounts, servers, or metadata layers.
- Scrape, crawl, harvest data from, or reverse engineer any portion of the service.
- Intentionally submit false, altered, or malicious metric and logging data.
- Bypass system resource limits, abuse access APIs, or use the platform to violate regional laws.
11. Third-Party Dependencies
DevRails relies on external third-party infrastructure providers to run its core systems, including cloud hosting platforms, database managers, payment processors, email deployment engines, analytics suites, and chat applications like Telegram. You acknowledge that these external dependencies directly affect the delivery, timing, performance, and data processing of our application features.
12. Intellectual Property and Feedback Rights
Coll-Con owns all rights, titles, source code, design elements, visual branding, and system property linked to DevRails. You retain full ownership over your cloud account data and infrastructure project metadata.
If you submit product feedback, feature requests, or optimization suggestions, you grant Coll-Con an unrestricted, perpetual, royalty-free license to implement those ideas to improve the software without any financial obligation to you.
13. Privacy Cross-Reference
Our collection, storage, and use of your personal information is described comprehensively in our Privacy Policy. By using DevRails, joining our launch waitlists, or linking your developer configurations, you acknowledge that your data will be handled in accordance with that Privacy Policy.
14. Warranty Disclaimer and Limitation of Liability
DevRails is provided on an “as is” and “as available” basis. To the maximum extent permitted by applicable law, Coll-Con disclaims all warranties, express or implied. In no event shall Coll-Con be liable for any indirect, incidental, special, or consequential damages—including, but not limited to, actual Google Cloud billing surges, lost revenue, project business downtime, corrupted data, or total infrastructure interruption—arising out of or connected to your operation of this software.
15. Governing Law and Dispute Resolution
These Terms are governed entirely by the laws of the Republic of Indonesia. Any operational legal disputes or claims arising out of your relationship with DevRails will be resolved exclusively in the competent courts of Jakarta, Indonesia, unless applicable regional law strictly requires otherwise.
16. Contact Information
For questions regarding these terms, subscription cancellations, or data requests, please contact us directly at our official support email: support@thecollcon.com.