Terms of Service

These Terms govern access to and use of Verixos by Aurora Technologies, including the Verixos websites, SaaS application, APIs, SDKs, CLI tools, MCP integrations, webhooks, documentation, demo environments, support channels, and self-host license workflows.

By creating an account, accessing Verixos, using a demo or trial, configuring an integration, uploading Customer Content, or using Verixos on behalf of an organization, you agree to these Terms and represent that you have authority to bind the organization you represent.

These Terms govern use of the Verixos websites, SaaS application, APIs, SDKs, CLI tools, MCP integrations, webhooks, documentation, demo environments, support channels, and self-host license workflows unless a separate signed agreement states otherwise.

If a customer has a signed order form, master services agreement, data processing addendum, self-host license addendum, support addendum, statement of work, or government procurement document, that signed document controls to the extent it conflicts with these online Terms.

Enterprise, GovCloud, air-gapped, on-prem, classified, controlled-unclassified, ITAR, EAR, export-controlled, defense, or agency deployments must be handled under a separate written agreement approved for that environment.

Customer Content means data, files, thermal models, CAD-derived data, material definitions, node networks, solver inputs, simulation results, exports, reports, comments, project metadata, API payloads, webhook payloads, and other content submitted to or generated through Verixos by or for a customer.

Engineering Output means simulation results, thermal predictions, solver diagnostics, advisor findings, validation artifacts, benchmark comparisons, exports, reports, charts, recommendations, or other engineering analysis generated through Verixos.

Restricted Data means data or projects that may be subject to export controls, ITAR, EAR, sanctions, government procurement restrictions, controlled-unclassified-information requirements, contractual handling requirements, or customer-specific security rules.

Users must provide accurate account information, protect credentials, maintain secure devices, and promptly report suspected unauthorized access.

Organization administrators are responsible for user invitations, roles, team memberships, SSO/SAML configuration, MFA policies, billing administration, API-key governance, webhook destinations, restricted-project access, and offboarding.

A customer is responsible for activity under its accounts, API keys, service credentials, SSO identities, self-host administrators, and automated integrations unless the activity is caused by Verixos breach of these Terms.

Academic access is the only free access path. It is intended for eligible students, educators, and approved academic research groups and may require a .edu email address, institutional verification, manual review, or renewal.

Verixos does not offer a broadly available public free commercial plan. Demo access, trials, previews, pilots, coupons, academic accounts, and beta access may be limited, revoked, or converted to paid access according to the applicable offer.

Academic users may not use academic access for paid commercial work, production contractor work, export-controlled programs, agency deliverables, or restricted customer work unless Verixos approves that use in writing.

Paid plans may be purchased through Stripe checkout, invoices, order forms, or procurement workflows. Customers authorize Verixos and its payment processor to charge applicable fees, taxes, renewals, usage charges, and approved overages.

Subscription fees are generally billed in advance and non-refundable except where required by law or stated in an order form. Usage-based fees, if enabled, may be billed after the applicable usage period.

Customers are responsible for taxes, duties, withholding, purchase-order accuracy, procurement approvals, vendor onboarding, and maintaining valid billing contacts. Enterprise, GovCloud, self-host, and air-gapped pricing requires a separate written order.

Plan limits, including node limits, concurrent simulation limits, advisor limits, API access, support level, export formats, and deployment rights, are enforced by the product and may differ by plan or signed order.

Verixos is engineering analysis software. Engineering Output depends on user inputs, geometry quality, material properties, assumptions, boundary conditions, solver configuration, mesh/readiness state, version, validation scope, and user interpretation.

Unless expressly stated in a signed agreement, Engineering Output is not a certification, design approval, flight sign-off, launch-readiness determination, safety approval, regulatory approval, government acceptance, or substitute for professional engineering judgment.

Customers are responsible for independent verification and validation, peer review, configuration control, test correlation, safety margins, mission assurance, quality procedures, and final engineering decisions.

Benchmarks, parity evidence, heritage reproductions, and validation artifacts describe specific tested cases. They do not guarantee accuracy for every model, mission, spacecraft, payload, environment, or operating condition.

As between the parties, Customer owns Customer Content. Verixos does not claim ownership of Customer Content.

Customer grants Verixos a limited license to host, process, transmit, display, secure, back up, troubleshoot, analyze, and otherwise use Customer Content as needed to provide, support, secure, bill, and improve the services, subject to the Privacy Policy and any signed agreement.

Customer represents that it has all rights, authorizations, export-control determinations, third-party permissions, and contractual approvals needed to upload, process, share, export, and use Customer Content in Verixos.

Customer must not upload third-party proprietary files, restricted data, controlled technical data, personal information, or government data unless the customer has confirmed the deployment, account, and written agreement are appropriate for that data category.

Verixos may provide deterministic advisor checks and optional external AI-assisted analysis. AI-assisted output may be incomplete, inaccurate, or unsuitable for a customer use case and must be reviewed by qualified personnel.

For restricted-project workflows, the product is designed to disable external LLM synthesis and use deterministic checks only. Customers remain responsible for confirming that organizational settings and deployment controls match their data-handling obligations.

Customers must not submit Restricted Data to an external AI path unless the customer has independently approved that provider, region, contract, retention terms, and data-use terms for the specific data category.

Customers are responsible for determining whether Customer Content, users, recipients, projects, deliverables, or use cases are subject to export controls, ITAR, EAR, sanctions, government procurement rules, controlled-unclassified-information requirements, classified-data restrictions, agency security requirements, or contractual flowdowns.

Verixos includes controls such as restricted-project flags, US-person-oriented fields, data-residency gates, MFA hooks, audit events, deterministic-only advisor behavior, and deployment evidence for self-host, GovCloud, and air-gapped use cases. These controls are technical aids and do not by themselves create legal compliance, export authorization, accreditation, ATO, ITAR registration, agency approval, or government certification.

Customers may not use the public SaaS for classified information, controlled nuclear information, export-controlled technical data, ITAR technical data, CUI requiring a dedicated authorized environment, or other restricted government data unless Verixos has approved that deployment in a signed agreement.

Customers may not use Verixos in violation of sanctions, embargoes, restricted-party rules, export licensing obligations, anti-corruption laws, government ethics rules, procurement-integrity rules, or agency-specific security requirements.

Customers using SSO/SAML are responsible for identity-provider configuration, domain enforcement, authorization mapping, user lifecycle, MFA policy, assertion integrity, and prompt removal of users who no longer need access.

API keys, SDKs, CLI tools, MCP integrations, and webhooks are for authorized automation only. Customers are responsible for securing secrets, rotating keys, validating endpoints, limiting scopes, monitoring usage, and preventing unintended disclosure through logs, repositories, tickets, prompts, or CI systems.

Verixos may rate-limit, suspend, revoke, rotate, or require migration of API keys, webhook integrations, or preview interfaces to protect the service or comply with law, security requirements, or product changes.

Self-host, GovCloud, on-prem, and air-gapped deployments require separate written terms defining permitted environments, license scope, seat limits, renewal process, support level, update mechanism, telemetry settings, backup and restore responsibilities, vulnerability-management obligations, and customer infrastructure responsibilities.

Offline license validation is designed to run locally using signed license files. Customers are responsible for protecting license files, renewal request files, signing keys under their control, deployment artifacts, backups, and administrators.

For customer-managed deployments, the customer is responsible for network controls, access controls, endpoint security, patching, monitoring, incident response, evidence retention, local compliance configuration, local data residency, and environmental validation unless a signed agreement assigns those duties to Verixos.

Customers and users must comply with the Acceptable Use Policy. They may not bypass access controls, attack systems, upload malware, abuse resources, scrape restricted data, reverse engineer protected components, interfere with other users, or use the service unlawfully.

Customers may not remove notices, circumvent plan limits, resell access without authorization, benchmark for competitive publication without written permission, or use Verixos to develop a competing service except where prohibited by law.

The service may interoperate with third-party services such as payment processors, identity providers, email providers, hosting providers, databases, analytics, error monitoring, AI providers, storage, customer webhook endpoints, and customer infrastructure.

Third-party services are governed by their own terms and privacy policies. Verixos is not responsible for customer-controlled third-party services or customer webhook endpoints.

Open-source components included with Verixos remain subject to their applicable open-source licenses. Nothing in these Terms limits rights granted directly under those licenses.

Beta, demo, trial, preview, validation, benchmark, and experimental features may be incomplete, unsupported, rate-limited, changed, suspended, or removed. They should not be used for production engineering decisions unless expressly approved in writing.

Demo content may be synthetic, seeded, simplified, or public-reference material and should not be treated as customer-confidential or mission-specific validation evidence.

Non-public business, product, pricing, roadmap, security, benchmark, beta, deployment, support, and technical information disclosed under circumstances indicating confidentiality should be treated as confidential unless a separate agreement states otherwise.

Each party must use reasonable care to protect the other party's confidential information and may use it only to exercise rights or perform obligations under these Terms or an applicable written agreement.

Verixos may suspend or restrict access if it reasonably believes an account, integration, deployment, or use case threatens security, violates law, violates these Terms, risks harm to users or infrastructure, creates abuse risk, or may expose restricted data in an unauthorized environment.

Customers must promptly notify Verixos of suspected unauthorized access, compromised credentials, leaked API keys, webhook misdelivery, export-control concerns, or security incidents involving Verixos.

Support level, response targets, uptime commitments, maintenance windows, backup obligations, and service credits apply only if stated in a signed order form, support addendum, or SLA.

Verixos may modify, improve, discontinue, or deprecate features, APIs, integrations, limits, or documentation, subject to any written enterprise commitments.

Except as expressly stated in a signed agreement, the service, documentation, demos, APIs, SDKs, benchmarks, AI advisor output, and Engineering Output are provided as is and as available.

To the maximum extent permitted by law, Verixos disclaims all warranties, whether express, implied, statutory, or otherwise, including warranties of accuracy, fitness for a particular purpose, non-infringement, merchantability, uninterrupted operation, error-free results, and that Engineering Output will meet any particular mission, safety, procurement, regulatory, or certification requirement.

To the maximum extent permitted by law, Verixos will not be liable for indirect, consequential, incidental, special, exemplary, punitive, lost-profit, lost-revenue, lost-data, mission-delay, launch-delay, procurement, cover, business-interruption, or engineering-decision damages, even if Verixos has been advised of the possibility of those damages.

Except for amounts owed for fees, misuse of Verixos, infringement of intellectual-property rights, confidentiality breaches, or violations of export-control, sanctions, government-use, or acceptable-use obligations, each party's aggregate liability arising out of or relating to these Terms is limited to the amounts paid or payable to Verixos for the service giving rise to the claim during the twelve months before the event giving rise to liability.

Customer will defend and indemnify Verixos from third-party claims arising from Customer Content, customer-controlled systems, unauthorized use, breach of these Terms, violation of law, infringement caused by customer materials, export-control violations, sanctions violations, government-use violations, or misuse of the service.

Verixos will defend and indemnify Customer from third-party claims alleging that the Verixos software, as provided by Verixos and used according to these Terms, directly infringes a United States patent, copyright, or trademark, excluding claims caused by Customer Content, customer instructions, third-party services, unsupported modifications, combination with non-Verixos materials, beta features, or use outside the applicable documentation.

The indemnified party must promptly notify the indemnifying party, allow reasonable control of the defense, and cooperate at the indemnifying party's expense. The indemnifying party may not settle a claim in a way that admits fault or imposes non-monetary obligations on the indemnified party without consent.

Either party may terminate according to the applicable online plan, order form, or signed agreement. Verixos may terminate or suspend for material breach, non-payment, security risk, unlawful use, export-control risk, or misuse.

Upon termination, customer access may end and Customer Content may be deleted after a retention period unless legally required or contractually agreed otherwise. Customers should export required engineering records before termination or plan downgrade.

These Terms are governed by the laws of the State of Delaware, excluding conflict-of-law rules. The state and federal courts located in Delaware have exclusive jurisdiction for disputes arising from or relating to these Terms, except that either party may seek injunctive or equitable relief in any court of competent jurisdiction.

The parties waive jury trial rights to the maximum extent permitted by law. Class actions and representative proceedings are not permitted; claims must be brought only on an individual basis unless applicable law prohibits this waiver.

Notices to Verixos must be sent to support@auroratechnologies.xyz and any additional notice address stated in an applicable order form. Notices to customers may be sent through the product, email, account administrator, billing contact, or written agreement.

Neither party may assign these Terms without the other party's consent except to an affiliate or in connection with a merger, acquisition, corporate reorganization, or sale of substantially all assets. Invalid provisions will be modified or severed while preserving the remaining Terms.

Questions about these Terms can be sent to support@auroratechnologies.xyz.