- Towards data freedom

Creating your personal server

Joining a freezr server

The easiest way to use freezr is to join an existing server. (Multiple people can use the same freezr server if the server owner allows it.) For example, is also a freezr server, and it allows you to set up a limited 'experimental' account, giving each user 3Mb of storage. But you can also 'bring your own storage', storing your data on dropbox, and point to your own Mongo-comaptible database. If you do that, you can store as much data as you like (cause it's your storage!) and freezr then just acts like a 'thin client' holding your credentials and helping to serve your apps and data to you.. for your dropbox via the freezr server to your browser.


Installing a new freezr server

You can also install your freezr in just a few minutes on an actual physical server, or on various cloud services such as Heroku and Amazon AWS, or, for the easiest option try freezr on replit or glitch.


  • Set up your freezr on replit or glitch, in just a few seconds.
  • Install freezr on your own computer or a development server
  • Install freezr on cloud servers such as Heroku
  • Initial Parameters

    When you first set up your freezr server, you need to set the initial parameters: the first (admin) user's name and password to access the site, as well as your choices for storage system and database - ie where freezr should store your files and data.

    If you are setting your freezr up on a local server or using services like replit and glitch, you can choose to use the local file system. But most cloud based servers delete any additional files every time they reboot, so you would need to use outside storage services (like AWS's S3) and store your credentials (tokens) on your server platform's environment variables. Once these are set up, then freezr will read them at launch and offer you to store your files there. Current choices are:

    File System Choices

  • Dropbox file system
  • Amazon AWS's S3
  • A few notes
  • All files,including apps and user data will be stored under a folder called "users_freezr"
  • A system user called 'fradmin' will be created, and within fradmin's files, you will see a file appear called freezr_environment.js which also has your database credentials and any access token in it - so do not let any one see this!
  • Other file systems, from google drive to blockchain based dairdrive have worked on freezr, and have APIs (in need of updating) to run your file system if you like. Other file systems can be easily added by integrating the set of file system APIs used in this implementation of freezr.
  • Database Choices

    freezr uses mongodb as the core database, not least because other companies provide mongodb-compatible databases, and so freezr users are not locked into any one company.

  • Using your file system as a a database.
  • Using Mongo's Atlas as your database.
  • A local mongo instance (for development)
  • Preferences

  • Under preferences, you can allow other users onto your server and set other preferences
  • You can also skip this and go straight to installing apps for your freezr server.