I Am Me I Am Free

Getting Started with I Am Me I Am Free

I run this on my home server and for most people it is a solid piece of open-source self-hosted software. It gives you control over your data without relying on third-party cloud services. The setup is straightforward if you know Docker, but there are a few gotchas I have learned the hard way. The project lives on GitHub under the name I Am Me I Am Free and you can grab the latest release at https://github.com/iAmMeIaMFreek/iAmMeIaMFreek. The repository includes a docker-compose.yml file that handles most of the dependencies for you.

What I Am Me I Am Free Actually Does

At its core it is a self-hosted personal data management platform. It lets you store notes, bookmarks, documents, and calendar events locally instead of uploading everything to someone else's servers. The main interface is a web dashboard that supports markdown, file uploads, and basic tagging. What most people do not realize is that it also includes a built-in encryption layer for sensitive files. You can set a master key during installation and every encrypted item is wrapped with AES-256 before it touches disk. This is not optional and you cannot retroactively encrypt unencrypted content without re-uploading it.

Installation Walkthrough

I am going to skip the fluff and get right into the steps that actually matter. I have installed this five times across different setups and I keep making the same mistakes so you do not have to. You need a machine running Linux, preferably Ubuntu 22.04 or Debian 12. Docker and docker-compose must already be installed and accessible to your user. If you are running this on a VPS make sure port 8080 or whatever port you choose is open in your firewall. The software does not require much RAM. Two gigabytes is plenty. Four is comfortable. First, create a project directory and pull the compose file. I usually do this by cloning the repo directly:

git clone https://github.com/iAmMeIaMFreek/iAmMeIaMFreek.git && cd iAmMeIaMFreek Before running docker-compose up, you need to create a .env file in the same directory. Copy the example from env.example and fill in at least these values: ADMIN_PASSWORD, ENCRYPTION_KEY, and DATABASE_URL. The database defaults to PostgreSQL so your connection string should look something like postgresql://iammeiamfree:password@db:5432/maindb. Here is where I almost always mess up. The default docker-compose.yml maps the database container to port 5432 on the host. If you already have PostgreSQL running locally you will get a port conflict. I solved this by changing the host-side mapping to 5433 in the compose file before the first run.

Once the env file is ready, run: docker-compose up -d Wait about thirty seconds and check the logs with docker-compose logs -f iammeiamfree. You should see the application initialize, connect to the database, and start serving. Navigate to http://your-server-ip:8080 and create your admin account.

Common Pitfalls

One thing that catches people out is the volume mounting. By default the compose file mounts a named volume for the database and a bind mount for user uploads. If you ever remove the container and the volumes by accident you lose everything. I learned this after wiping a test instance that had three months of imported data. Now I run regular backups to an external directory. Another issue is the encryption key. If you lose your ENCRYPTION_KEY from the .env file, every encrypted item becomes permanently unreadable. There is no recovery mechanism. Write it down somewhere physical. Not in your password manager. In physical form.

Configuration and Daily Use

After installation the default settings work fine for a personal setup. If you want external access you will need a reverse proxy. I use Nginx with Let's Encrypt because it keeps things simple and free. Add a server block that proxies / to localhost:8080 and make sure you pass the correct Host header. Without the Host header the app breaks authentication on redirects. The tagging system is functional but basic. You can tag anything with multiple labels and filter by them. There is no nested tag support so keep your tag names flat and descriptive. I settled on a three-tag maximum per item and it has worked well enough. For the document storage piece, I import PDFs and images regularly. The upload limit is 25MB per file by default. You can change this in the admin settings but I would not push it past 100MB unless you have a dedicated SSD backing the uploads. The search index builds in the background and can cause high CPU usage for a few minutes after a bulk import. This is normal and it stops on its own.

I Am Me I Am Free Export and Migration

The export feature is underdocumented but useful. You can export everything as a JSON bundle including tags and file references. The JSON does not include the actual binary files though, only their paths. If you plan to migrate to another instance, you need to copy the uploads directory separately. I used rsync for this and it took about twelve minutes for roughly 400 files totaling around eight gigabytes. I want to be clear about what this tool does not do well. There is no real-time collaboration. The comment system exists but it is basic and not meant for team workflows. If you need shared workspaces with multiple active editors, look at something like Nextcloud or Outline instead. The mobile experience is decent but not native. You access it through a browser. PWA installation works on both iOS and Android but the browser-based app does not support background sync. If you add items offline they will not appear until you open the app again and it checks in with the server.

Password management is not its purpose. Yes you can store passwords in the notes section but it is not a replacement for a proper password manager. I stopped trying to use it for that after I realized my backup strategy was inadequate for credential-level security.

Bottom Line

I Am Me I Am Free is a capable self-hosted alternative for people who already have a server and want a private workspace. It is not beginner-friendly out of the box and the documentation assumes you already understand Docker and basic networking. If that describes you it is worth the time investment. If you need something that just works without any setup, you are better off paying for a hosted solution.