· · eCommerce Builder

Which Database and Server for a Small Digital Site

Which Database and Server for a Small Digital Site
Reading time8 min
Length1,800 words
Last updatedNovember 13, 2026
LevelBeginner

If you ask an AI assistant what database a Django site needs, it will often say Postgres. It sounds like the serious, grown-up answer. But is it the right one for a small digital business? The best way I know to answer that is to picture two different sites and ask what each of them needs.

Both sites in this article are made up. The software, the server needs and the trade-offs are real. This is for people who run Djangify on their own server with Self-Hosted. If you use Managed Hosting, the database and the server are my job and you can skip to the end.

Key takeaways
  • SQLite keeps the whole database in one file inside the application. It is simple, light and the default in Djangify.
  • Postgres is a separate database server built for many people reading and writing at once.
  • A small digital business usually has few writes, so SQLite is often the better fit.
  • Switch when you see database locked errors, expect bursts of orders, or want more than one application server.
  • Self-hosted needs a VPS running Ubuntu with at least 1 GB of RAM, and 2 GB is recommended.

What a database does

Your site needs somewhere to keep its products, orders, customers, blog posts and settings. That somewhere is the database. Both SQLite and Postgres do that job. The difference is how they are built.

SQLite

  • Everything lives in a single file inside your application
  • Nothing extra to install and no separate password for the database
  • Uses very little memory, so a small server is enough
  • Easy to back up: copy the file, your media folder and your .env file
  • Handles one write at a time, so heavy bursts of writes queue up

Postgres

  • A separate database program running beside your application
  • Built for many people reading and writing at the same moment
  • Can live on another machine or be a hosted database service
  • Needs installing, a user and password, its own updates and its own backups
  • Uses more memory, because a second program is running

Site one: planners and a free tool on SQLite

Picture Tom. He sells printable habit planners and a small bundle of worksheets, and he has a free habit tracker on his site that brings in a steady trickle of visitors. A good day for Tom is a dozen orders. A new account here, a blog edit there, a couple of downloads. Nothing happens in a rush.

For a site like Tom's, each sale is a small event and not thousands of them a second. SQLite handles that comfortably. It has nothing to configure, so there is one less thing that can go wrong at two in the morning, and it keeps the server small and cheap. When Tom wants a backup, he copies one file along with his media folder and his .env file, and he has everything.

Tom does not need to think about his database very often, and that is the point. The simplicity is a real benefit when you are the person looking after the server.

Site two: launch days on Postgres

Now picture Imani. She teaches a short course in budgeting for new parents and sells it with a workbook and a few paid tools. Most weeks look like Tom's. But twice a year she launches a new version to a mailing list of thousands, and in the first hour a few hundred people try to register, pay and download all at once.

That is a different kind of day. Lots of people are writing to the database at the same moment: new accounts, new orders, new download records. SQLite lets one thing write at a time, so under that kind of pressure the writes queue, and occasionally a visitor might see a database is locked error at the worst possible moment. Postgres was designed for exactly this situation, and it is the usual choice for busy applications.

Imani also likes the idea of keeping her database on a hosted database service, separate from her application, so the application server can be rebuilt without touching her data. That is another thing Postgres makes possible, and SQLite does not.

The price she pays is more to look after. Postgres needs installing, a user and a password, its own updates, and its own backups. It also uses more memory. For Imani that is worth it. For Tom it would be a cost with no benefit.

When it is time to swap

Nobody can give you an exact number of orders where SQLite stops being enough, because it depends on your server and on how your site is used. What you can do is watch for signs. Tom should consider Postgres if any of these start to apply to him.

Staying and switching

SQLite is still fine when

  • Orders and sign-ups arrive a few at a time
  • You have one application server
  • You want the simplest backups
  • You want the cheapest server that works

Postgres starts to make sense when

  • You see database is locked errors regularly
  • You expect many orders or sign-ups at the same time
  • You want to run more than one application server
  • You prefer a hosted database service, or you are comfortable running Postgres

Djangify uses SQLite by default, because it keeps hosting simple and cheap and suits the kind of business it is built for. Postgres is available as an option for the owners who need it. Postgres is not better in every case. It is better for a different case, and the sensible choice fits the size of the job.

The server underneath

Whichever database you choose, a self-hosted Djangify site runs on a server you rent. Shared hosting does not work. You need a VPS, which is a virtual server of your own.

What your server needs
Item Minimum Recommended
Operating system Ubuntu 22.04 Ubuntu 24.04 LTS
CPU 1 core 2 cores
Memory 1 GB 2 GB

Hetzner and DigitalOcean are two popular places to rent one, and Linode and Vultr also work. Check the current price and availability on the day you sign up, because prices and plans change, and look for a plan with at least 2 GB of memory. Pick a server location close to your customers.

The word unmanaged simply means the provider gives you a blank server and looks after the hardware, while you or your AI assistant install and look after the software. Djangify's install guide is written for exactly that. The set-up has a clear order:

  1. Create an account and a projectEverything you create lives inside the project.
  2. Make an SSH keyA safer way to log in than a password. Share the public key only, never the private one.
  3. Create a firewallAllow TCP 22 for logging in, and TCP 80 and 443 for web traffic and HTTPS.
  4. Add the serverChoose Ubuntu, a plan with at least 2 GB of memory, your SSH key and your firewall.
  5. Point your domain at itAdd an A record in your domain registrar's settings that points to the server's address.
  6. Hand over to your AIThe install guide is written to be handed to your AI assistant, which walks you through the rest for your own server.
Keep it safe

Never share your private SSH key and keep a backup of it somewhere safe. Do not paste passwords or keys into an AI chat. Type them into your own files on the server. Turn on your provider's backup option if you want an extra safety net, and keep your own backups of the database, the media folder and the .env file.

Find your fit

Answer three quick questions and the quiz will point at the option that suits you today. You can take it again whenever your site changes. The answer is saved in this browser.

Quiz

Which setup fits you?

  1. Who looks after your server?
    • My AI assistant will walk me through it
    • I would rather someone else handled it
    • I am comfortable running databases myself
  2. What does a busy day look like?
    • A handful of orders spread across the day
    • A launch with lots of people paying within minutes
    • I do not know yet and I would like it handled
  3. How many application servers will you run?
    • One
    • More than one
    • None, I want no servers to think about

SQLite on one small server

This is the default and the simplest. It suits steady, small orders and gives you the easiest backups.

See Self-Hosted

Worth looking at Postgres

Bursts of orders or several application servers are the cases Postgres is built for. Start from the install guide.

Read the install guide

Managed Hosting

I look after the servers, the backups and the security updates, so you have no database to choose.

See Managed Hosting

The boxes on this page are Djangify content blocks. The free ones are explained in this free article, and the quiz is a premium block. A demo product on this site, How to Set Up an Affiliate Shop Without Uploading a Product, shows how a page with premium blocks is put together.

Questions

Can I switch from SQLite to Postgres later?

Yes. Postgres is an option, not a one-way door, and your AI assistant can walk you through the change. Make a full backup of your database, media folder and .env file before you start.

Does Managed Hosting use SQLite or Postgres?

That is part of the service I run, so you never have to choose or look after it.

What does a database is locked error mean?

With SQLite, one thing can write at a time. If many writes arrive together they queue, and occasionally one gives up. Seeing it once is not a crisis. Seeing it regularly is a sign to look at Postgres.

Which provider should I pick?

Both Hetzner and DigitalOcean work. Choose a server location close to your customers and the plan whose price and screens you are comfortable with.

Summary
  • SQLite is one file, simple and light. Postgres is a separate server built for heavy simultaneous use.
  • Tom's steady orders suit SQLite. Imani's launch-day bursts are the kind of case Postgres is built for.
  • Switch when you see locked errors, expect bursts, or want more than one application server.
  • Pick a VPS with Ubuntu and at least 2 GB of memory, and keep your own backups.
Keep reading

Self-Hosted or Managed Hosting

Which way to run your site and what each includes.

Read more →

What 10% Costs You on 100 Sales

The sums behind owning your own site.

Read more →

No Domain? No Problem

Launching on a djangify.com subdomain with Managed Hosting.

Read more →