The official Files.com provider for Terraform — the standard tool for managing infrastructure as code — lets you write your whole Files.com setup as version-controlled HCL. Users, groups, permissions, folders, remote servers, automations, and sign-in — all written in code, reviewed in pull requests, and applied with the same Terraform workflow you already use for your cloud.
Files.com publishes an official, open-source Terraform provider on the HashiCorp Terraform Registry. Because every Files.com action runs through the API — with nothing that only works in the web console — the provider can manage nearly the whole platform in code: users, groups and permissions, folders, remote-server mounts, automations, behaviors, notifications, and sign-in methods.
Manage Files.com the same way your team already manages everything else: version-controlled code, reviewed in pull requests, deployed the same way across dev, staging, and prod, with a full git history of every change. Write down how you want your site set up in HCL, run terraform apply, and the provider makes the live site match.
The same way you already manage your cloud — written down, reviewed, and repeatable — applied to how your file transfer platform is set up.
Write down your whole site — users, folders, permissions, automations, integrations — in HCL (Terraform’s configuration language). Every setup is predictable and repeatable, instead of being clicked together by hand and drifting out of sync between dev, staging, and prod.
Your Files.com setup lives in git right next to the rest of your infrastructure. Every change can be reviewed, compared, and rolled back, and the commit history tells you who changed what, when, and why.
Spin up a new environment, onboard a team, or build a new client’s folders and automations by running one reusable module — no setting things up by hand.
Your setup written in code, plus the Files.com audit log, shows exactly how the site is configured and everything that has changed — the trail a SOC 2 review or an auditor asks for.
Every action on Files.com runs through the API, with nothing that only works in the web console. So the provider can manage just about the whole site — there’s no setting you can click in the console that you can’t also write in code.
Deploy one module to dev, staging, and prod so all three sites stay exactly the same.
Set up the folders, groups, permissions, and automations for a new tenant from code in one run.
Review Files.com changes in pull requests and let CI deploy them alongside the rest of your stack.
Run terraform plan to spot any manual change someone made outside of code, measured against the setup you declared.
Add the provider, give it a Files.com API key, and write down the resources you want. The provider uses HCL and the standard Terraform workflow — terraform plan and terraform apply — the same two commands you use to manage your cloud. It can manage nearly the whole site: users, groups, permissions, folders, remote servers (the S3, Azure, GCS, and other mounts), automations, behaviors, notifications, and sign-in methods including SAML.
Managing Files.com in code runs on the same API as the SDKs and CLI — it’s part of the platform, not a paid add-on. The provider docs live on the Terraform Registry and at files.com/docs.
What teams ask about the provider, the resources it manages, authentication, and where it’s published.
The official Files.com Terraform provider is published on the HashiCorp Terraform Registry at registry.terraform.io/providers/Files-com/files. Add it like any other provider — declare it in your required_providers block and run terraform init.
The Files.com Terraform provider manages nearly the entire site as code: users, groups, permissions, folders, remote server mounts (Amazon S3, Azure Blob, Google Cloud Storage, and the rest), automations, behaviors, notifications, and sign-in methods including SAML. Every setting that exists in the web console runs through the API, so it has a Terraform resource.
The Files.com Terraform provider authenticates with a Files.com API key, set as a provider argument. Scope the key to the permissions your configuration needs; every change it makes is recorded in the Files.com audit log like any other API activity.
Yes. The Files.com Terraform provider runs on the same REST API as the Files.com SDKs and CLI — it is part of the platform, not a paid add-on. The provider, the official SDKs, and the CLI all reach the same endpoints, so anything you can do in one you can do in the others.
Workspaces can be created and managed with Terraform through the Files.com API. Child sites cannot — standing up a child site provisions infrastructure (its own domain, TLS certificate, and tenant) that runs through the web interface. Use Terraform for the users, folders, permissions, and automations inside a site, and the console to stand up a new child site.
Yes. The Terraform provider is included with every Files.com plan at no extra charge, because it uses the same API as the rest of the platform. You need a Files.com account and an API key — there is no separate license or add-on for infrastructure as code. See pricing for plan details.
Write down your users, folders, permissions, and automations in HCL, then run terraform apply to make 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