Terms of Use
DevAgents OS
Responsible company: PULSEFLOW TECNOLOGIA LTDA
CNPJ: 62.683.137/0001-45
Last updated: May 2026
These Terms of Use govern access to and use of the DevAgents OS website, platform, services, demonstrations, assessments, content, agents, integrations, automations, images, packages, components, licenses, and related resources.
DevAgents OS is a product currently maintained by PULSEFLOW TECNOLOGIA LTDA, registered under CNPJ No. 62.683.137/0001-45. For the purposes of these Terms, the expressions “DevAgents OS”, “we”, “us”, “our”, or “platform” refer to the product, services, agents, components, resources, and digital channels currently operated, provided, or licensed by PULSEFLOW TECNOLOGIA LTDA.
By accessing, browsing, registering, requesting a demonstration, submitting information, participating in an assessment, contracting services, using agents, running licensed components, activating a license, or interacting with DevAgents OS, the user declares that they have read, understood, and agreed to these Terms of Use.
If you do not agree with these Terms, you must not access, use, run, copy, install, integrate, activate, or contract DevAgents OS.
1. Acceptance of Terms
Use of DevAgents OS implies full acceptance of these Terms of Use and any other policies, contracts, proposals, service descriptions, privacy notices, or specific conditions applicable to the services used.
If the user accesses, uses, or contracts DevAgents OS on behalf of a company, organization, client, or third party, the user declares that they have authority to accept these Terms on behalf of that entity and to bind it to the obligations described herein.
These Terms may be supplemented by commercial proposals, service agreements, confidentiality agreements, data processing agreements, purchase orders, statements of work, licensing terms, support policies, technical annexes, or other specific contractual documents.
In the event of conflict between these Terms and a signed contractual instrument, the specific contractual instrument shall prevail within the scope of the contracted services.
2. General Service Description
DevAgents OS provides a software engineering platform and related services based on the orchestration of specialized agents across the software development lifecycle.
Our services may include, among others:
- institutional and technical content about agentic software engineering;
- assessments of engineering flows, bottlenecks, risks, quality, security, DevOps, observability, and metrics;
- demonstrations and proof-of-concept activities;
- orchestration of specialized agents across the software development lifecycle;
- integration with tools already used by client teams;
- generation of technical artifacts, recommendations, analyses, documentation, evidence, metrics, and automation support;
- provision of licensed components, images, packages, runtimes, agents, workflows, or distributions for execution in the client’s own environment;
- governance layers for strategic, tactical, and operational visibility;
- consulting, technical guidance, implementation support, updates, and continuous improvement services.
DevAgents OS organizes specialized agents throughout the software development lifecycle, from discovery to operations, to expand the capacity of technology teams, reduce bottlenecks, and create a continuous improvement flow driven by data.
Each stage of the lifecycle may involve a specialized agent. These agents may share context, preserve traceability, and integrate with tools already used by the team.
3. DevAgents OS Delivery Models
DevAgents OS may be made available to the client through different models, according to the commercial proposal, agreement, technical scope, or contracted modality.
3.1. Managed Service by DevAgents OS
Under the managed service model, DevAgents OS may operate, configure, orchestrate, or support the execution of specialized agents, select providers, models, tools, infrastructure resources, processing mechanisms, and technical flows necessary to deliver the contracted services.
In this model, DevAgents OS may process information, artifacts, documents, code, logs, metrics, tickets, technical data, and other inputs provided by the client for the purpose of generating deliverables, analyses, recommendations, automations, documentation, evidence, diagnostics, or technical artifacts.
The selection of providers, models, infrastructure, and processing mechanisms may be made by DevAgents OS according to technical, operational, commercial, security, availability, cost, performance, region, maturity, and use-case adequacy criteria, subject to the contracted scope, Privacy Policy, applicable contractual instruments, and instructions agreed with the client.
In this model, fees may be charged for the service, configuration, operation, support, model consumption, API calls, processing, infrastructure, temporary storage, observability, maintenance, or other resources necessary for the execution of the contracted scope, according to the applicable commercial proposal or agreement.
3.2. License for Execution in the Client’s Infrastructure
Under the licensing model for client infrastructure, DevAgents OS may provide the client with an image, package, container, component, runtime, distribution, agent, workflow, or set of licensed resources for execution in the client’s own, controlled, or contracted environment.
In this model, the client may use its own infrastructure, cloud accounts, API keys, artificial intelligence models, databases, observability tools, repositories, management systems, pipelines, security environments, and other technical resources necessary for operation.
DevAgents OS may provide periodic updates, fixes, improvements, new features, security adjustments, agent revisions, workflow updates, or new versions, according to the contracted plan, support policy, update cycle, or applicable agreement.
Execution of DevAgents OS in the client’s own environment shall be conditioned on the existence of a valid license, authorized activation, and a validation mechanism defined by DevAgents OS, which may include a certificate, key, token, activation code, digital signature, environment identifier, periodic verification, or other equivalent technical mechanism.
The client shall be responsible for the infrastructure, security, availability, configuration, costs, permissions, connectivity, credentials, internal policies, compliance, models used, contracted providers, and processing of data within its own environment, except for matters expressly assumed by DevAgents OS in the agreement.
3.3. Hybrid Model
DevAgents OS may be contracted under a hybrid model, combining managed service, technical support, licensed components, execution in the client’s environment, specific integrations, periodic updates, consulting, governance, remote support, or continuous monitoring.
The responsibilities of each party, access limits, involved environments, processed data, licenses, costs, models used, retention, support, SLAs, updates, and security obligations must be defined in the applicable contractual instrument.
4. AI, Cloud, and Third-Party Service Providers
DevAgents OS was designed to operate agnostically with respect to models, clouds, artificial intelligence providers, automation tools, observability tools, security tools, development tools, and engineering management tools.
DevAgents OS may use, integrate with, or allow the configuration of third-party services, including, by way of example and without limitation, artificial intelligence providers, language models, cloud services, vector databases, observability tools, code repositories, management tools, automation platforms, and security services, such as OpenAI, Anthropic, Google, Microsoft Azure, AWS, Meta, DeepSeek, Kimi/Moonshot, Hugging Face, LangChain, LangGraph, CrewAI, AutoGen, and others.
References to third-party providers in these Terms are merely illustrative and non-exhaustive. They do not imply partnership, affiliation, representation, endorsement, permanent availability, universal certification, obligation of use, or guarantee of integration with any specific provider.
The use of third-party services shall be subject to each provider’s terms of use, privacy policies, security policies, technical limits, costs, availability, regions, retention rules, training rules, data usage rules, commercial conditions, and restrictions.
Under the managed service model, DevAgents OS may select the providers most appropriate for the use case, subject to the contracted scope and the applicable confidentiality, security, and data protection commitments.
Under the execution-in-client-infrastructure model, the client may configure its own providers, models, cloud accounts, API keys, and internal policies, assuming responsibility for the costs, limits, compliance, availability, and terms of such third parties.
DevAgents OS shall not be responsible for acts, omissions, failures, outages, pricing changes, policy changes, technical limitations, security incidents, API unavailability, model changes, blocks, regional restrictions, or contractual changes of third-party providers.
5. Specialized Agents and Deliverables
Depending on the service scope, DevAgents OS may support or provide specialized agents such as:
- Requirements Agent — epics, user stories, acceptance criteria, and requirement structures based on meetings, demands, and business inputs;
- Architecture Agent — component mapping, technical decisions, architectural documentation, risk analysis, and solution design support;
- Code Agent — code generation support, review, refactoring suggestions, documentation, and recommendations aligned with engineering standards;
- Quality Agent — automated tests, Gherkin scenarios, coverage analysis, traceability, and test strategy support;
- Security Agent — SAST, DAST, threat modeling, dependency analysis, AppSec controls, and security validation support;
- DevOps Agent — CI/CD pipelines, deployment automation, environment diagnostics, failure analysis, and operational support;
- Observability Agent — logs, metrics, traces, operational insights, alerts, and root cause analysis support;
- Metrics Agent — lead time, cycle time, throughput, bottlenecks, flow efficiency, and continuous improvement indicators;
- Modernization Agent — legacy system analysis, rule extraction, documentation, refactoring support, and modern code generation support.
The scope, availability, limitations, integrations, outputs, and responsibilities of each agent may vary according to the contracted service, technical environment, client maturity, tool access, and implementation phase.
6. Artifacts, Results, and Operational Records
DevAgents OS aims to support the generation of technical and operational artifacts, such as documents, analyses, code, reports, scripts, evidence, recommendations, metrics, risk maps, technical decisions, traceability, diagnostics, and improvement proposals.
The final result of the services may be delivered as an artifact, document, file, report, dashboard, script, configuration, code, recommendation, evidence, technical package, or other agreed format.
Depending on the contracted model, certain technical data, metadata, usage records, logs, license data, operational history, support information, execution evidence, consumption metrics, and information necessary for service provision may be stored for control, security, audit, billing, support, licensing, improvement, traceability, and contractual compliance purposes.
The storage, retention, and processing of personal data shall be governed by the DevAgents OS Privacy Policy and the applicable contractual instruments.
7. Governance Layer
In addition to specialized agents, DevAgents OS may provide a governance layer with strategic, tactical, and operational visibility.
This layer may include support for:
- OKRs and engineering goals;
- team performance indicators;
- delivery metrics;
- quality metrics;
- security indicators;
- operational indicators;
- bottleneck analysis;
- continuous improvement tracking;
- traceability between business needs, technical decisions, code, tests, security controls, delivery, and operations.
Metrics, dashboards, analyses, and recommendations are intended to support decision-making and continuous improvement. They should not be interpreted as absolute guarantees of performance, productivity, compliance, quality, security, or business outcomes.
8. Assessments and Initial Evaluation
The adoption process may begin with an assessment of the client’s current engineering flow.
The assessment may analyze where time is lost, where bottlenecks exist, which risks are present, and which specialized agents may be most appropriate for the real context of the team.
Assessment results, recommendations, technical opinions, maturity analyses, and roadmap suggestions are provided based on available information, interviews, artifacts, system access, tool data, and evidence shared by the client.
The accuracy and usefulness of an assessment depend on the completeness, accuracy, and quality of the information provided by the client.
9. Eligibility and User Responsibilities
By using DevAgents OS, the user represents and warrants that:
- they have legal capacity to accept these Terms;
- they will use the platform only for lawful, professional, and legitimate purposes;
- they will provide accurate, complete, and up-to-date information when interacting with DevAgents OS;
- they will not impersonate any person or organization;
- they will not misuse forms, contact channels, demonstrations, agents, integrations, licensed components, or services;
- they have authorization to submit any data, files, documents, code, logs, metrics, repositories, tickets, or technical artifacts made available to DevAgents OS;
- they will comply with all applicable laws, regulations, contractual obligations, intellectual property rules, confidentiality obligations, and data protection requirements.
The user is responsible for all actions performed through their access, credentials, systems, integrations, infrastructure, licenses, or authorized representatives.
10. Acceptable Use
The user agrees to use DevAgents OS responsibly and only for legitimate professional purposes.
The user must not:
- use DevAgents OS for unlawful, fraudulent, abusive, harmful, discriminatory, defamatory, or unauthorized purposes;
- attempt to compromise the security, integrity, availability, or performance of the platform;
- attempt to gain unauthorized access to systems, accounts, data, agents, integrations, environments, or infrastructure;
- use automated mechanisms for scraping, mass extraction, credential stuffing, vulnerability exploitation, or abusive traffic generation;
- reverse engineer, decompile, copy, clone, reproduce, or attempt to derive the source code, architecture, agent logic, prompts, workflows, license mechanisms, certificates, validations, operating models, or proprietary methods of DevAgents OS, except where expressly permitted by law or written authorization;
- reproduce, distribute, resell, sublicense, commercialize, or make available any content, agent structure, methodology, documentation, visual resource, platform resource, image, package, runtime, container, component, license, or deliverable without express authorization;
- bypass, remove, tamper with, clone, circumvent, or interfere with license mechanisms, validation mechanisms, certificates, tokens, activation codes, time limitations, access controls, or technical protections;
- use DevAgents OS to train, develop, replicate, or support a competing product, unless expressly authorized in writing;
- extract, copy, or reuse prompts, workflows, agent structures, governance models, orchestration rules, proprietary methodologies, or internal logic of DevAgents OS;
- upload malware, malicious code, exploit scripts, credential stealers, ransomware, or any harmful component;
- submit confidential, personal, sensitive, regulated, or third-party data without proper authorization and adequate protection;
- use the platform to violate intellectual property rights, privacy rights, trade secrets, contractual obligations, or legal restrictions;
- interfere with the normal operation of DevAgents OS or any third-party service integrated with it;
- use outputs generated by agents without appropriate human review when such outputs may affect security, production environments, compliance, legal matters, financial decisions, employment decisions, or other material outcomes.
DevAgents OS may suspend, restrict, or terminate access if misuse, security risk, legal violation, abuse, or breach of these Terms is identified.
11. License, Activation, and Use Validation
When DevAgents OS is made available through a license, the client receives a limited, temporary, non-exclusive, non-transferable, non-sublicensable, and revocable license, according to the conditions defined in the commercial proposal, agreement, order form, licensing term, or equivalent instrument.
The license may be conditioned on a certificate, key, token, activation code, digital signature, environment identifier, periodic validation, expiration control, or other technical mechanism defined by DevAgents OS.
The license may limit or condition, among other aspects:
- term of use;
- number of environments;
- number of users;
- number of agents;
- available features;
- processing volume;
- update frequency;
- support scope;
- enabled integrations;
- use in production, staging, development, or demonstration;
- territory, client, project, CNPJ, cloud account, or authorized environment.
It is prohibited to copy, resell, sublicense, redistribute, lend, share, clone, publish, expose, transfer, make available to third parties, or use the license outside the contracted limits.
Any attempt to bypass or remove license, activation, validation, expiration, certificate, key, token, or technical control mechanisms constitutes a material breach of these Terms and may result in suspension or termination of access, without prejudice to any applicable legal measures.
DevAgents OS may perform periodic license validations to verify eligibility, term, integrity, authorized environment, version, authenticity, and use compliance. License unavailability, failure, expiration, or invalidation may prevent or limit the operation of licensed components.
12. Technical Validation for Execution in the Client’s Environment
When DevAgents OS is made available for execution in the client’s own, controlled, or contracted infrastructure, prior technical validation may be required to assess feasibility, compatibility, security, connectivity, permissions, network restrictions, internal policies, compliance requirements, authorized providers, and other conditions necessary for proper operation.
This validation may consider, among other aspects:
- architecture of the client’s environment;
- security, firewall, proxy, network, authentication, and access control policies;
- external or internal connectivity restrictions;
- availability of required cloud services, AI models, APIs, and tools;
- permissions to run containers, images, runtimes, agents, or components;
- observability, logging, audit, and retention policies;
- compliance, privacy, and data segregation requirements;
- compute capacity, scalability, latency, and performance;
- compatibility with providers, models, databases, tools, and integrations desired by the client;
- minimum CPU, memory, storage, runtime, orchestrator, DNS, certificates, secrets, proxy, connectivity, and technical dependency requirements.
Environments with restrictive policies, high security levels, network blocks, lack of permissions, API limitations, execution restrictions, lack of connectivity, or specific audit requirements may require technical adjustments, complementary architecture, additional scope, specific validation, or separate contracting.
DevAgents OS does not guarantee that all resources will operate in any client environment without prior assessment, proper configuration, necessary permissions, minimum requirements being met, and technical validation. The existence of a valid license does not, by itself, guarantee full compatibility with the infrastructure, internal policies, providers, configurations, tools, or restrictions chosen by the client.
Failure to meet minimum technical requirements, required permissions, documented dependencies, or connectivity and execution conditions may limit, degrade, or prevent the operation of DevAgents OS, without such event being characterized as a failure of the solution or breach by DevAgents OS.
13. Restricted, Offline, Air-Gapped, and High-Security Environments
Execution of DevAgents OS in highly restricted, offline, air-gapped, segregated, regulated, or externally blocked environments shall follow premises similar to those used in enterprise software deployments within the client’s infrastructure.
In such scenarios, deployment may require specific technical assessment, dedicated architecture, special package, specific license, differentiated activation, offline or hybrid validation, manual updates, complementary documentation, differentiated support, prior homologation, additional security procedures, and specific commercial conditions.
Execution in a restricted environment may depend on requirements such as:
- formal homologation process by the client;
- approval of architecture, security, network, infrastructure, and operations;
- controlled release of images, packages, checksums, signatures, SBOMs, or technical evidence, when applicable;
- activation procedure compatible with an environment without external access or with limited connectivity;
- defined process for applying updates, fixes, patches, and new versions;
- agreed mechanism for validating license, integrity, version, and authorized environment;
- definition of responsibilities for backup, logs, monitoring, incidents, availability, disaster recovery, and continuity;
- definition of limits for telemetry, metadata, license validation, and operational record collection.
Deployment in a restricted environment does not imply disclosure of source code, internal prompts, orchestration logic, proprietary methodology, or protected internal components. DevAgents OS may provide technical evidence, documentation, reports, SBOMs, checksums, signatures, release notes, or security information when applicable and agreed, without this representing assignment, exposure, or transfer of the proprietary core of the solution.
When the client’s environment prevents online license validation, automatic updates, telemetry, provider connectivity, API access, or remote support, alternative procedures, a specific plan, manual updates, operational windows, versioned packages, offline validation, and support under specific commercial conditions may be required.
DevAgents OS shall not be responsible for unavailability, limitation, update failure, support delay, incompatibility, loss of functionality, or degradation resulting from restrictions imposed by the client’s environment, internal policies, network blocks, lack of connectivity, lack of permissions, corporate security tools, infrastructure incompatibilities, or changes made by the client.
14. Technical Audit, Scans, and Security Evidence
Any technical audit, penetration test, vulnerability scan, image inspection, container analysis, SBOM analysis, load test, behavior analysis, dependency review, CVE verification, or security assessment of DevAgents OS components must be previously authorized and limited to the agreed scope.
DevAgents OS may provide, when applicable and according to contract, technical evidence, security documentation, release notes, checksums, signatures, SBOMs, vulnerability reports, hardening guidance, responsibility matrix, or information necessary for the client’s homologation process.
Such evidence does not grant the client the right to access, extract, copy, modify, decompile, disassemble, reconstruct, circumvent, clone, or reverse engineer source code, prompts, license mechanisms, internal logic, proprietary architecture, orchestration flows, or other protected components of DevAgents OS.
Tests, audits, or scans that cause unavailability, degradation, license violation, improper exposure, reverse engineering, unauthorized modification, integrity breach, or improper access may result in license suspension, support restriction, or the adoption of applicable legal measures.
15. Visibility Limits, Code Access, and Core Protection
When DevAgents OS is executed in the client’s infrastructure through an image, container, package, runtime, component, agent, workflow, or licensed distribution, the client shall have access only to the elements necessary for operation, configuration, integration, data input, data output, permitted logs, documented parameters, and generated artifacts, according to the contracted scope.
The availability of DevAgents OS for execution in the client’s environment does not grant access to source code, internal prompts, proprietary guidelines, orchestration logic, internal architecture, decision rules, internal flows, governance mechanisms, agent structures, prompt engineering strategies, evaluation models, license mechanisms, protected components, know-how, trade secrets, or other elements that make up the proprietary core of the solution.
The client may have visibility over inputs, outputs, permitted configurations, authorized integrations, produced artifacts, defined operational logs, and evidence required for the contracted audit, but shall not have the right to inspect, extract, copy, modify, reconstruct, derive, or access the protected internal components of DevAgents OS.
DevAgents OS must not be interpreted as delivery of source code, transfer of intellectual property, assignment of technology, disclosure of prompts, provision of internal methodology, or unrestricted delivery of the product’s engineering structure.
Any need for technical audit, security validation, compliance analysis, controlled review, complementary documentation, or specific evidence must be previously agreed in writing, subject to confidentiality, intellectual property, security, and protection limits of the DevAgents OS core.
16. AI Models, Connectors, and Specific Customizations
DevAgents OS may support different providers, AI models, APIs, connectors, tools, and integration mechanisms, according to technical availability, contract, scope, and operational feasibility.
The inclusion, modification, or combination of specific providers, models, connectors, or flows requested by the client may require technical assessment, security analysis, compatibility validation, architectural adjustments, additional development, testing, homologation, component updates, or additional contracting.
The existence of support for a given provider or model does not imply an obligation to support all of its versions, modalities, configurations, limits, APIs, regions, formats, features, or possible combinations.
Specific requests, such as simultaneous use of multiple models, routing between models, fallback between providers, use of non-certified models, integration with private APIs, adaptation for local models, inclusion of a new connector, use of less common providers, or changes to the orchestration strategy, may be treated as additional scope and shall be subject to assessment, approval, timeline, cost, feasibility, and specific technical conditions.
DevAgents OS may refuse, limit, or condition integrations, models, providers, or configurations that present security risk, instability, technical incompatibility, disproportionate cost, policy violation, low reliability, contractual limitation, or negative impact on service quality.
17. Updates, Versions, and Support
DevAgents OS may provide periodic updates, fixes, improvements, security adjustments, new versions, agent changes, workflow updates, compatibility changes, new connectors, or technical adjustments.
Access to updates may depend on the contracted plan, license validity, payment status, support scope, contracting modality, or applicable agreement.
DevAgents OS does not guarantee permanent compatibility with all previous versions, environments, integrations, dependencies, third-party providers, AI models, APIs, or client configurations.
The client is responsible for testing updates in an appropriate environment before applying them to production, unless otherwise expressly provided in a specific agreement.
Unless expressly contracted, the license does not include unlimited support, SLA, emergency assistance, production support, on-call service, assisted operation, advanced troubleshooting, customization, environment analysis, correction of client configuration, homologation of new models, deployment in restricted environments, or continuous monitoring.
Support levels, service channels, service hours, response times, resolution times, severities, maintenance windows, operational responsibilities, incident handling, and production support shall apply only when expressly provided in a contract, proposal, support plan, or equivalent document.
18. Telemetry, Licensing, and Technical Records
Even when executed in the client’s own environment, DevAgents OS may use technical telemetry mechanisms, license validation, version verification, integrity verification, activation, authorized environment verification, subscription status, authorized consumption, and minimum records necessary for security, audit, support, billing, updates, contractual compliance, and prevention of misuse.
Collection or validation may occur online, offline, or in hybrid form, depending on the contracted model, environment restrictions, the client’s security policy, and applicable commercial conditions.
Technical data collected for such purposes may include, as applicable, license identifier, version, authorized environment, activation status, integrity information, error events, usage metadata, technical metrics, update records, and information necessary to validate contracted use.
DevAgents OS shall not use telemetry mechanisms to grant the client access to the proprietary core of the solution, nor to transfer intellectual property to the client. The processing of personal data, when applicable, shall follow the Privacy Policy and applicable contractual instruments.
In offline, air-gapped, or highly restricted environments, lack of connectivity may require manual validation, periodic file exchange, offline license, specific certificate, manual update package, integrity procedure, operational window, or another mechanism compatible with the contracted enterprise model.
19. Supply Chain, Image Integrity, and Components
When DevAgents OS is made available through an image, container, package, runtime, component, or licensed distribution, the client must use only official, authorized, and intact versions provided by DevAgents OS.
DevAgents OS may provide, when applicable and contracted, checksums, signatures, release notes, SBOMs, technical documentation, installation instructions, minimum requirements, compatibility matrix, or build evidence to support internal security and homologation processes.
The client must not alter, recompose, disassemble, repackage, inject components, modify layers, remove protections, alter license mechanisms, redistribute modified versions, or run tampered images of DevAgents OS without express written authorization.
Unauthorized changes to images, packages, containers, runtimes, dependencies, protected configurations, or licensed components may invalidate support, contractual warranty, license validation, operational responsibility, and update rights.
DevAgents OS shall not be responsible for failures, vulnerabilities, incidents, unavailability, incompatibilities, or losses resulting from unauthorized changes, unofficial images, modified components, injected dependencies, recomposed builds, or redistributions made by the client or third parties.
20. Client Data, Technical Artifacts, and Access Permissions
During assessments, demonstrations, proof-of-concept activities, or contracted services, the client may provide DevAgents OS with access to technical artifacts, systems, tools, environments, or data.
Such materials may include, among others:
- documents, diagrams, and technical specifications;
- epics, stories, tasks, tickets, and acceptance criteria;
- repositories, code snippets, pull requests, branches, and commits;
- logs, metrics, traces, dashboards, incidents, and operational events;
- CI/CD pipelines, configuration files, scripts, and deployment information;
- quality, testing, coverage, and security reports;
- architecture decisions, risks, dependencies, roadmaps, and business rules;
- legacy system documentation and modernization artifacts.
The client remains responsible for ensuring that:
- it has the right and authorization to share such materials with DevAgents OS;
- access permissions are configured according to the principle of least privilege;
- unnecessary, excessive, sensitive, confidential, or regulated data is removed, masked, anonymized, or minimized whenever possible;
- credentials, tokens, secrets, API keys, and access grants are properly managed and revoked when no longer needed;
- DevAgents OS is informed of any specific security, confidentiality, retention, regulatory, or contractual restriction applicable to the materials provided.
21. Outputs Generated by Agents
DevAgents OS may generate or support the generation of outputs such as documentation, code suggestions, test scenarios, security findings, architecture recommendations, metrics, diagnostics, reports, automation scripts, and modernization proposals.
All outputs generated by agents must be treated as technical support material and should be reviewed, validated, tested, and approved by qualified professionals before adoption, especially in production environments.
DevAgents OS does not guarantee that agent-generated outputs will be error-free, complete, secure, compliant, suitable for every environment, or fit for a specific purpose without human validation.
The client is responsible for evaluating and approving the use of outputs in its own systems, products, environments, repositories, pipelines, processes, and business decisions.
Artifacts, reports, diagnostics, recommendations, metrics, and other results produced by DevAgents OS reflect the information, data, access, context, versions, configurations, tools, and evidence available at the time of generation.
Updates, reprocessing, continuous synchronization, new analyses, context reassessments, artifact review, or generation of new versions shall depend on the contracted scope, data availability, permissions, integrations, technical consumption, and applicable commercial conditions.
Incomplete data, inconsistent documents, inaccurate transcripts, truncated logs, lack of history, code without standards, conflicting metrics, insufficient permissions, misconfigured environments, or outdated information may affect the quality, accuracy, completeness, and usefulness of generated artifacts.
Unless otherwise contractually provided, the client may use delivered artifacts for its internal engineering, operations, governance, modernization, documentation, quality, and continuous improvement purposes. The client may not resell, redistribute, package, sublicense, publish, commercially use, or exploit the artifacts in a way that creates, trains, develops, or favors a product, methodology, agent, automation, or service competing with DevAgents OS.
22. Artificial Intelligence Limitations
DevAgents OS uses agentic workflows, automation, and artificial intelligence techniques to support software engineering activities.
The user acknowledges that artificial intelligence systems may produce incomplete, inaccurate, outdated, inconsistent, insecure, or unsuitable outputs. AI-generated recommendations may also depend on the context, quality of input data, tool permissions, model limitations, and configuration decisions.
Use of DevAgents OS does not replace:
- professional engineering judgment;
- software architecture responsibility;
- code review;
- security validation;
- legal, privacy, or compliance review;
- production testing;
- operational monitoring;
- approval by responsible stakeholders;
- internal governance controls.
The user agrees not to rely exclusively on agent-generated outputs for critical decisions without appropriate human review and validation.
23. Account, Access, and Security
If DevAgents OS provides user accounts, administrative access, API access, agent configuration, integration credentials, or other restricted resources, the user is responsible for maintaining the confidentiality and security of their access credentials.
The user must not share credentials with unauthorized persons, store secrets insecurely, bypass access controls, or allow unauthorized use of their account or integrations.
The user must immediately notify DevAgents OS if they suspect unauthorized access, credential compromise, security incident, or misuse involving the platform or related services.
DevAgents OS may implement security controls, access restrictions, monitoring, logging, authentication mechanisms, permission reviews, and other measures to protect the platform, users, clients, and systems.
24. Intellectual Property
All rights, title, and interest in DevAgents OS, including but not limited to software, platform structure, agent concepts, workflows, methodologies, architecture, interfaces, designs, visual assets, texts, documentation, content, trademarks, trade names, technical materials, know-how, prompts, orchestration logic, license mechanisms, images, packages, runtimes, containers, components, and proprietary processes, belong to DevAgents OS, PULSEFLOW TECNOLOGIA LTDA, or their licensors, as applicable.
Access to or use of DevAgents OS does not transfer to the user any intellectual property rights, ownership rights, license rights, or commercial exploitation rights, except as expressly provided in a written agreement.
The user may not copy, reproduce, modify, adapt, translate, distribute, publish, sell, sublicense, reverse engineer, create derivative works from, or commercially exploit any part of DevAgents OS without prior written authorization.
The client retains ownership of its own pre-existing data, documents, systems, code, repositories, business information, technical artifacts, and intellectual property provided to DevAgents OS.
Unless otherwise agreed in writing, deliverables specifically produced for a client under a paid engagement may be governed by the applicable proposal, agreement, statement of work, or service agreement.
25. Confidentiality
During the use of DevAgents OS, assessments, demonstrations, or contracted services, the parties may have access to confidential information, including technical, commercial, operational, strategic, financial, security, product, architectural, or business information.
The receiving party must protect confidential information with reasonable care, use it only for authorized purposes, and not disclose it to unauthorized third parties.
Confidentiality obligations may be further defined in a confidentiality agreement, commercial proposal, service agreement, data processing agreement, or other applicable contractual instrument.
26. Data Protection and Privacy
The processing of personal data by DevAgents OS is governed by its Privacy Policy and, where applicable, by specific contractual instruments between DevAgents OS and the client.
By using DevAgents OS, the user acknowledges that personal data may be processed in accordance with the DevAgents OS Privacy Policy.
When the client provides personal data to DevAgents OS, the client is responsible for ensuring that there is a valid legal basis, proper authorization, transparency to data subjects, and compliance with applicable data protection laws.
Under the execution-in-client-infrastructure model, the client shall be responsible for the processing of data carried out within its own environment, including internal policies, security, retention, access, location, contracted providers, and regulatory compliance, unless otherwise specifically provided in a contract.
27. Commercial Conditions, Costs, and Paid Services
Certain features, assessments, implementations, integrations, support levels, consulting services, enterprise capabilities, model usage, API consumption, infrastructure, licenses, updates, validations, or components may be subject to a commercial proposal, agreement, subscription, usage limits, fees, payment terms, taxes, service scope, renewal rules, cancellation rules, or other specific conditions.
Under the managed service model, fees may consider, among other factors, technical scope, number of agents, processing volume, model consumption, API calls, infrastructure usage, configuration effort, support, integrations, storage, operation, observability, and maintenance.
Under the licensing model for client infrastructure, fees may consider, among other factors, license, term of use, number of environments, number of agents, updates, support, validation, deployment, maintenance, contracted modules, and applicable technical limits.
Costs of third-party providers used directly by the client, such as cloud, AI models, databases, observability tools, APIs, repositories, or external platforms, shall be the responsibility of the client, unless expressly provided otherwise.
When the client uses its own keys, tokens, accounts, credentials, models, cloud providers, gateways, APIs, or third-party tools, the client shall be responsible for costs, usage limits, billing, permissions, credential rotation, security, blocks, leaks, unavailability, retention rules, data policies, model training, compliance, and other obligations associated with such third parties.
Consumption, cost, performance, number of calls, tokens, processing, storage, embeddings, reranking, OCR, multimodal models, agent execution, logs, reprocessing, or infrastructure usage estimates are indicative only and do not constitute a fixed-cost guarantee, unless expressly contracted.
Reprocessing, increased volume, use of premium models, provider changes, multiple models, additional integrations, scope expansion, increased retention, continuous execution, restricted environment, differentiated support, or new features may generate additional costs.
Unless expressly stated otherwise, information available on the website does not constitute a binding commercial proposal, guaranteed availability, fixed price, final scope, or unconditional service commitment.
Commercial conditions shall be valid only when formalized by an authorized proposal, order form, agreement, statement of work, invoice, or equivalent document.
28. Availability and Changes to the Platform
DevAgents OS may update, modify, suspend, discontinue, replace, restrict, or remove features, content, agents, integrations, resources, workflows, demonstrations, components, images, packages, licenses, or services at any time for technical, security, operational, legal, commercial, or strategic reasons.
We do not guarantee that the platform, website, agents, integrations, licensed components, or services will be uninterrupted, error-free, permanently available, compatible with all systems, or free from failures.
Whenever possible and reasonable, relevant changes may be communicated through appropriate channels.
29. Disclaimers
DevAgents OS is provided on an “as is” and “as available” basis, except where expressly agreed otherwise in a written agreement.
To the maximum extent permitted by applicable law, DevAgents OS does not provide warranties of:
- uninterrupted operation;
- error-free outputs;
- absolute security;
- full compatibility with all environments;
- permanent compatibility with all AI providers, cloud providers, APIs, tools, or integrations;
- guaranteed productivity gains;
- guaranteed cost reduction;
- guaranteed compliance;
- guaranteed security remediation;
- guaranteed software quality;
- guaranteed business results;
- suitability for a specific purpose without proper assessment, configuration, implementation, and validation.
Any examples, metrics, references, demonstrations, benchmarks, or illustrative materials presented by DevAgents OS are for informational purposes and may not reflect the specific reality of each client.
30. Limitation of Liability
To the maximum extent permitted by applicable law, DevAgents OS and PULSEFLOW TECNOLOGIA LTDA shall not be liable for indirect, incidental, special, punitive, exemplary, consequential, or loss-of-profit damages arising from or related to the use of the platform, services, agents, outputs, recommendations, integrations, licensed components, images, packages, licenses, or content.
DevAgents OS shall not be responsible for damages, losses, incidents, failures, or decisions resulting from:
- incorrect, incomplete, outdated, or insufficient information provided by the user or client;
- unauthorized sharing of data, code, credentials, logs, documents, or technical artifacts;
- misuse of the platform, agents, outputs, licensed components, or integrations;
- improper execution in the client’s infrastructure;
- incorrect, insufficient, or insecure configurations performed by the client;
- selection, use, or contracting of models, cloud providers, APIs, or third-party tools by the client;
- lack of human review, testing, validation, or approval of agent-generated outputs;
- failures, outages, restrictions, security incidents, or changes in third-party tools, models, APIs, or platforms;
- implementation decisions made solely by the client or by third parties;
- production incidents resulting from unvalidated use of suggestions, scripts, code, configuration, or automation;
- attempts to bypass license, certificate, key, token, activation code, or validation mechanism;
- events beyond the reasonable control of DevAgents OS.
Nothing in these Terms excludes or limits liability where such exclusion or limitation is prohibited by applicable law.
31. Suspension, Termination, and License Deactivation
DevAgents OS may suspend, restrict, or terminate access to the platform, services, demonstrations, agents, integrations, components, licenses, updates, or resources if it identifies:
- breach of these Terms;
- security risk;
- unauthorized use;
- illegal activity;
- abusive behavior;
- violation of intellectual property rights;
- violation of privacy or data protection obligations;
- misuse of credentials, systems, agents, integrations, components, or outputs;
- attempt to bypass license, certificate, token, key, expiration, or validation mechanisms;
- use outside the contracted scope;
- non-payment, where applicable;
- risk to DevAgents OS, clients, users, third parties, or infrastructure.
The user may stop using DevAgents OS at any time. Contracted services and licenses may be subject to specific clauses regarding termination, cancellation, notice, payment, deactivation, return, deletion, retention, and survival, as provided in the applicable agreement.
Upon termination, expiration, cancellation, definitive suspension, or non-renewal of the license, the client must immediately cease use of DevAgents OS, stop executions, remove or deactivate images, containers, packages, components, runtimes, keys, certificates, tokens, activation codes, and unauthorized copies, as well as revoke related access and integrations, unless expressly authorized otherwise.
DevAgents OS may preserve minimum records necessary for billing, audit, license proof, fraud prevention, security, contractual compliance, regular exercise of rights, and legal or regulatory obligations, according to the Privacy Policy and applicable law.
Clauses related to confidentiality, intellectual property, core protection, limitation of liability, use of artifacts, reverse engineering restrictions, payment, audit, data protection, and obligations that by their nature must survive termination shall remain valid after termination of the contractual relationship or license.
32. Benchmarks, Publicity, Brand, and Disclosure of Results
The client may not publish benchmarks, commercial comparisons, load tests, performance measurements, public analyses, evaluation results, comparative studies, screenshots, reports, marketing materials, or disclosures using the name, brand, visual identity, results, or references to DevAgents OS without prior written authorization.
DevAgents OS also will not use the client’s name, brand, logo, case study, testimonial, environment, data, or results for commercial, advertising, public presentation, or institutional material purposes without prior authorization, unless permitted by contract.
Public references to integrations, providers, clients, results, metrics, gains, costs, productivity, or performance must observe confidentiality, intellectual property, data protection, trade secrets, technical context, and applicable authorization.
33. Roadmap, Demonstrations, and Future Features
Information about roadmap, future features, prototypes, demonstrations, plans, forecasts, concepts, experiments, versions under development, or resources not yet available is informational only and does not constitute a delivery obligation, availability guarantee, commercial commitment, or binding deadline, unless expressly provided in a signed agreement.
DevAgents OS may change, postpone, replace, cancel, or restructure future features, integrations, agents, connectors, supported models, resources, and evolution plans for technical, commercial, strategic, legal, operational, or security reasons.
34. Changes to These Terms
These Terms of Use may be updated periodically to reflect legal, regulatory, technological, functional, commercial, security, operational, licensing, or service scope changes.
The latest version will be made available through the website, platform, or other appropriate channels. Continued use of DevAgents OS after changes become effective constitutes acceptance of the updated Terms.
If the user does not agree with the updated Terms, they must stop using DevAgents OS.
35. Governing Law and Jurisdiction
These Terms shall be governed by the laws of the Federative Republic of Brazil, without prejudice to any mandatory rights granted to users under applicable local laws.
Unless otherwise defined in a specific agreement, any disputes related to these Terms or to the use of DevAgents OS shall be submitted to the competent courts of Brazil, subject to applicable legal rules.
36. Contact
For questions about these Terms of Use, please use the contact channels available on the DevAgents OS homepage.
DevAgents OS
A product currently maintained by PULSEFLOW TECNOLOGIA LTDA
CNPJ: 62.683.137/0001-45
Specialized agent orchestration for the software development lifecycle.