Terms

Terms and Conditions

These terms describe the basic rules for using ForgedBase and the responsibilities that come with managing connected infrastructure.

This page is provided for product transparency. If you need a signed agreement or legal review copy, contact us before relying on this summary.

Account and workspace responsibilities

You are responsible for the users, teams, workspaces, connected providers, sites, servers, domains, databases, backups, deployments, commands, and applications you manage through ForgedBase.

Keep account access secure, review invited members carefully, remove users who no longer need access, and make sure workspace activity is authorized by the organization that owns the infrastructure.

Connected providers

ForgedBase uses the provider credentials you connect to provision and manage resources on your behalf. You remain responsible for provider charges, limits, account status, and provider terms.

If a provider account, API token, OAuth connection, DNS zone, repository, mail provider, storage provider, or billing account changes outside ForgedBase, related ForgedBase actions may fail until the connection is updated.

Acceptable use

Do not use ForgedBase to host illegal content, distribute malware, send abusive mail, attempt unauthorized access, bypass third-party provider terms, interfere with other users, or compromise infrastructure.

Do not use automation, API keys, deployments, commands, backups, or provider sync to overload ForgedBase, provider APIs, shared networks, or systems you do not control.

Plans, billing, and limits

Plan limits, feature access, API access, usage allowances, billing status, and provider-side quotas may affect what can be created or operated through ForgedBase.

Third-party providers may charge separately for infrastructure, storage, DNS, mail, bandwidth, snapshots, backups, or other resources created through connected accounts.

Customer content and backups

You retain responsibility for content, code, database records, uploaded files, secrets, configuration files, backups, and exports stored in or generated from the resources you manage.

ForgedBase backup and restore features are operational tools, not a guarantee that every resource can be recovered in every scenario. Keep independent backups when your own compliance, business continuity, or recovery needs require them.

Availability, support, and changes

We work to keep ForgedBase reliable, but infrastructure services, provider APIs, DNS, SSL issuance, deployments, backups, and integrations can be affected by external systems.

ForgedBase may update features, plans, limits, documentation, security controls, and operational workflows as the product evolves. Material changes may be communicated through the dashboard, email, documentation, or this page.

Suspension and termination

Access may be suspended or limited when required for security, abuse prevention, unpaid billing, provider restrictions, legal obligations, or protection of the service.

You may stop using ForgedBase by disconnecting providers, removing resources, exporting data you need, and closing the relevant account or workspace access where available.