Polysite

For organisations with more than one website

Run all your websites from one place.

One login. One set of updates. Every site keeps its own address, its own look and its own team. Built for campaigns, associations, charities and anyone tired of keeping five websites alive.

  • Beta
  • Source-available
  • Free for your own sites
  • Product sends no usage data
Example design: a one-weekend conference site
A conference
Example design: a day spa
A day spa
Example design: a help centre
A help centre

Does this sound familiar?

Five websites should not mean five of everything.

Five logins, five update days

Every site has its own sign-in and its own software to keep current. Something always gets forgotten.

Who is allowed to publish?

Changing it means an email to a developer and a wait. Meanwhile an old volunteer still has the keys.

The day it goes viral

The petition is shared everywhere, thousands arrive at once, and you find out whether the site holds.

Ten example designs, ready to use

Same engine. Nothing alike on the outside.

Each design is a complete, fictional example site that comes with Polysite. Use one as it is, restyle it, or start your own with a single command. Every name, person and picture is made up.

What you get

Everything a team needs, in plain terms.

Many sites, one place

Each site has its own domain, content, media and team. An editor of one site cannot see or change another.

Roles you edit yourself

Make a role such as "Newsletter editor", tick what it may do, save. No developer, no wait. Anything not ticked is blocked.

Build pages with blocks

Compose pages from ready-made blocks and preview them at phone, tablet and desktop widths before publishing.

Drafts, history, scheduling

Save a draft, compare versions, restore an old one, and schedule publishing for later.

Petitions and forms

One signature per person, a public count with a goal bar, consent built in, and old entries deleted on a timer.

Events and sign-ups

Event pages with a limit and a waiting list, calendar files, reminders and an attendee list.

Add only what you need

News, search, several languages, signed webhooks and more are plugins you add as folders. Take one out and nothing is lost.

Careful by default

Nightly backups, tested restores, a deploy that backs up first and rolls back on its own. No usage tracking.

Your own look

A site's whole look is one folder. Copy an example, change the colours, and a site is wearing it.

We tried to break it

A petition that kept every signature.

We sent thousands of signatures at a deliberately modest server, all at once. Every one was saved, none was counted twice. The test script is public, so you can try to break it on your own server.

Lab test on one machine: the app limited to 1 CPU and 1 GB, the test running alongside it. About 55 signatures a second. Treat it as an estimate and test your own server before a campaign. How petitions work.

3,457signatures sent
3,457signatures saved
0lost or doubled

Two ways in

See it with your own eyes.

For your team

Not technical? Good. Tell me about your sites and I will show you how they would work in one place, and what it would take to get there. No pitch, no obligation.

Book a walk-through

Working with a contractor or an agency? Ask me how the licence applies: me@iamharshdoshi.com.

For developers

Run it on your own computer with Docker and Git. About two minutes to build on the maintainers' machine.

git clone https://github.com/polysites/polysite.git && cd polysite
git clone https://github.com/polysites/polysite-themes.git themes
git clone https://github.com/polysites/polysite-plugins.git plugins
cp .env.example .env
docker compose -f docker-compose.yml -f docker-compose.dev.yml up -d --build
  1. Open http://polysite.localhost/admin.
  2. The setup page asks for your admin account and first site: use the domain examplesite.localhost, pick a theme, tick the starter home page.
  3. Open http://examplesite.localhost. Add examplesite2.localhost with another theme.

Needs ports 80, 443, 3000, 3001 and 5432 free and about 5 GB of disk. This is the hot-reload development setup, not production.

Where it stands, honestly.

Polysite is in beta. The core is built and tested, and I am looking for the first organisations to shape it with me. It is source-available, not open source: free to use and change for your own organisation's sites; building or hosting sites for clients for a fee needs a separate agreement. Polysite itself sends no usage data anywhere.

Built by Harsh Doshi at Quick Support Today, together with Claude, Anthropic's AI coding assistant. The automated tests and the documented list of past bugs are the record of what was checked. Licensing questions: info@quicksupporttoday.com.