Configuration As Code, Not Clicks
Define the site — users, folders, permissions, automations, integrations — in HCL for predictable, repeatable deployments instead of manual setup that drifts between environments.
Files.com publishes an official, open-source Terraform provider on the HashiCorp Terraform Registry. Because Files.com is API-first — every operation lives in the REST API, with no UI-only side channel — the provider can manage nearly every aspect of the platform as code: users, groups and permissions, folders, remote-server mounts, automations, behaviors, notifications, and authentication methods.
Manage Files.com the way your team already manages everything else — version-controlled code, reviewed in pull requests, deployed consistently across dev, staging, and prod, with a full git history of every change. Declare the desired state of your site in HCL, run terraform apply, and the provider reconciles the live site to match.
The same discipline you bring to cloud infrastructure, applied to the configuration of your file transfer platform.
Define the site — users, folders, permissions, automations, integrations — in HCL for predictable, repeatable deployments instead of manual setup that drifts between environments.
Files.com configuration lives in git next to the rest of your infrastructure, so every change is diffable, reviewable, and revertible. Who changed what, when, and why is answered by the commit history.
Stand up a new environment, onboard a team, or build a new client’s folder structure and automations by applying a module — no hand-configuration.
Code-based configuration plus the Files.com audit log gives full visibility into the site’s state and its change history — the trail a SOC 2 review or an auditor wants.
With 100% API coverage and no UI-only operation, the provider can manage essentially the whole site — there’s no setting you can click in the console but can’t codify.
One module deployed to dev, staging, and prod so the three sites stay identical.
Provision the folder tree, groups, permissions, and automations for a new tenant from code.
Files.com configuration reviewed in pull requests and deployed by CI alongside the rest of the stack.
terraform plan surfaces any out-of-band manual change against the declared state.
Add the provider, supply a Files.com API key, and declare your resources. The provider uses declarative HCL and the standard Terraform workflow — terraform plan and terraform apply — the same workflow you use to manage cloud infrastructure. It manages nearly the whole site: users, groups, permissions, folders, remote servers (the S3, Azure, GCS, and other mounts), automations, behaviors, notifications, and authentication methods including SAML.
Code-based management rides on the same REST API as the SDKs and CLI — it is part of the API-first surface, not a gated add-on. Provider documentation lives on the Terraform Registry and at files.com/docs.
Define your users, folders, permissions, and automations in HCL — then terraform apply makes the site match. Start a free trial and connect the provider with an API key.
No credit card required • Free for 7 days • Live in minutes