Skip to content

Free Server (Community)

free.flexfs is the admin server for flexFS Community edition. It provides the same core mount client deployment and volume configuration functionality as the Enterprise admin server, but is designed for single-volume deployments without a license key.

CapabilityCommunity (free.flexfs)Enterprise (admin.flexfs)
Volumes1Unlimited
End-to-end encryptionSupported
Proxy groupsSupported
configure.flexfsSupported
Dynamic CSI provisioningSupported
Volume quotasSupported
Volume tokens with mount-path scopingSupported
Multiple accountsSupported

The Community edition supports CSI static provisioning for Kubernetes. Dynamic provisioning requires Enterprise.

SubcommandDescription
startStart the free server
init credsInitialize the credentials file
init systemdCreate and enable a systemd service unit
deinit credsRemove the credentials file
deinit systemdRemove the systemd service unit
versionPrint the build version
licensePrint license information

Unlike the Enterprise admin server, free.flexfs init creds configures the entire single-volume deployment in one step. It generates all required tokens (account, metadata, and volume) automatically.

Terminal window
free.flexfs init creds \
--provider aws \
--region us-east-1 \
--api s3 \
--bucket my-flexfs-bucket \
--prefix flexfs \
--metaAddr meta-host:8443
FlagDefaultDescription
--provider(required)Cloud provider code (e.g., aws, gcp, azure, oci)
--region(required)Cloud region code (e.g., us-east-1)
--api(required)Block storage API code (e.g., s3, gcs, azure, oci)
--bucket(required)Object storage bucket name
--prefixflexfsKey prefix within the bucket
--metaAddr(required)Metadata server address (host:port)
--blockAddr(empty)Custom block storage endpoint (for S3-compatible stores)
--blockUser(empty)Block storage access key / username
--blockPass(empty)Block storage secret key / password
--retention604800Block retention period in seconds (default 7 days)
--forcefalseOverwrite an existing credentials file

The volume ID is derived deterministically from the bucket and prefix, so re-initializing with the same bucket and prefix produces the same volume.

The credentials file is TOML and contains all tokens, storage configuration, and the metadata server address:

accountToken = "$TOKEN"
metaToken = "$TOKEN"
volumeToken = "$TOKEN"
volumeID = "$TOKEN"
provider = "aws"
region = "us-east-1"
api = "s3"
bucket = "my-flexfs-bucket"
prefix = "flexfs"
metaAddr = "meta-host:443"
retention = 604800
Terminal window
free.flexfs start

The server reads its credentials file and starts the REST API. The credentials file must be initialized before the first start.

FlagDefaultDescription
--bindAddr0.0.0.0:443Address and port to bind
--noSSLfalseDisable TLS for the REST API
--noInstallerfalseDisable the /deploy/install-mount.sh installer endpoint
--sslCert~/.flexfs/ssl/certTLS certificate file path
--sslKey~/.flexfs/ssl/keyTLS private key file path
--credsFile~/.flexfs/free/credsCredentials file path (persistent flag)

Create and enable a systemd service unit:

Terminal window
sudo free.flexfs init systemd --now
FlagDefaultDescription
--nowfalseStart the service immediately after enabling
--startFlags(empty)Additional flags to pass to the start command
--forcefalseOverwrite an existing systemd unit file

This creates the unit file flexfs-free.service. Requires root.

Terminal window
sudo free.flexfs deinit systemd

Stops and removes the flexfs-free.service unit. Requires root.

Terminal window
free.flexfs deinit creds

Removes the credentials file. If the file is referenced by a systemd unit, the command refuses unless --force is passed.

FlagDefaultDescription
--forcefalseRemove credentials even if referenced by systemd units

The free server has the same TLS behavior as the Enterprise admin server: a self-signed certificate is generated automatically if none exists, and custom certificates can be provided via --sslCert and --sslKey.