Editions
BlixtFS comes in three editions. They share one codebase and one set of images; a license file decides which features are switched on.
Comparison
| Standard | Enterprise | High Performance | |
|---|---|---|---|
| Price | Free | Per server, per month | Per server, per month |
| Data and clients | Unlimited | Unlimited | Unlimited |
| Deployment | Single instance | Single instance | Clustered (scale-out) |
| NFSv4 and SMB | ✓ | ✓ | ✓ |
| All supported cloud providers | ✓ | ✓ | ✓ |
| NFSv3, SFTP, WebDAV | ✓ | ✓ | |
| Monitoring | ✓ | ✓ | |
| Admin tools | ✓ | ✓ | |
| Cache warming service | ✓ | ✓ | |
| Transparent failover | ✓ | ✓ | |
| Hot standby | ✓ | ||
| Replicated reads and writes | ✓ | ||
| Scale-out metadata and parallel I/O | ✓ | ||
| Support | Community | Commercial | Commercial |
Current prices are on the product page.
How the license works
A license is a signed file you receive from Blixt Software. You pass it to
BlixtFS with the --license flag or the LICENSE environment variable, either
as a path or as the file’s contents. BlixtFS checks it offline at startup, so
it needs no connection to a license server.
Without a license, or when a license has expired, BlixtFS keeps serving your data as the Standard edition: licensed features are switch off. Nothing is deleted and no data becomes unreachable.
See Licensing for installation and renewal.