🏰 Porta Pagi · a village portal

Your village on one page — private, quiet, and yours to keep.

A map of your hamlet where the things that must stay findable live: who is away, who is going to the shop, when the work party is, who has the ladder. Not a group chat. Not a social network. No ads, no trackers, nothing sold inside. What it counts is up to your village, and the default is nothing.

Walk through the demo Read what it refuses

€15 a month for the whole village. Every house included. Your own server, your own subdomain, your data exportable forever. Walk through a running one — no signup, no email.

The demo village's home screen: parcels on a cadastral map, each coloured by the crest of the house that lives there, a stream drawn through them, and the list of houses under the map.

It was said once. Then it was gone.

  • Is anyone going to town tomorrow?
  • … forty messages about the goats …
  • sorry, what was the answer?

A village chat holds everything and keeps nothing. The answer to "who has the ladder" is in there, somewhere under the goats. Porta Pagi gives each thing that must stay findable a room of its own, and puts the rooms on a map of your land.

The rooms

Every picture on this page is from the demo village. It is invented from the ground up: the houses, the land, the people, the year of life in it. Walk through it as any house; it is wiped and set right on the hour.

The village map with crests on parcels

The map

Who lives where. Your parcels, coloured by house crest. A house without land is a house all the same, and shows on the map whose land it lives on.

The Watchtower room: an away notice with dates, care notes and a watcher

Watchtower

"We are away from the 21st to the 3rd, please watch the land." Dates, care notes, one watcher, and a thread for "I fed them, key is back under the step". Only logged-in houses see it.

The Market room: needs, give-aways and shop runs

Market

"Going to the shop, anyone need anything?" Needs a house takes on, give-aways, and shop runs with a cut-off.

The Tavern room: pinned notices above the month calendar

Tavern

Pinned notices on top, the month calendar with work parties and sign-ups, and the message board under it. One room, because a village has one hall.

The Tool shed room: tools by house, who holds each one

Tool shed

Who lends what, and who holds it now. A nudge to bring it back after a day, then at doubling gaps: a reminder, not a ledger. Under it, the tools the village lacks, with the names of houses that would love one.

The Projects room: a job in progress, a planned one, a finished one

Projects

A long job split into tasks a house takes. Planned, in progress, finished, with a strip of pictures the chat would have lost in a week.

The Campground room: a camper arrived, a house has the money

Campground

A camper arrived; a house has the money; it is handed over. No amounts, no plates. Everyone hears an arrival and a claim, so nobody collects twice.

The Codex: the village's adopted text, section by section

Codex

The founding text your village hands a house before it joins. On paper it is signed once and never seen again. Here it sits at the head of the page, in your languages, and a house amends it with its name on the change.

The Contacts room: the well-driller, the vet, the fire brigade

Contacts

"Who did we call about the well last time?" A name, a number, a note. Any house writes one down and any house corrects a wrong number. Nothing rings: a number is looked up, not announced.

And a door for your assistant. A house mints a key in the Houses room, and its agent — Claude Code, or any client that speaks MCP over HTTP — acts as that house through the same door a phone uses. "Put the work party on the calendar for Saturday" is then in the Tavern. A house that runs no assistant sees nothing change.

What this will never do, and what is yours to ask for

The refusals are the product. A village that reads them and nods is the village this was built for.

Never

  • Ads. Not now, not in a free tier, not ever.
  • Trackers, analytics, third-party scripts. Neither in the portal nor on this page. View the source; there is no script tag on it.
  • Public pages. Nothing in the portal is readable without a house's login. No guesthouse page, no public calendar, no embed.
  • Anything sold inside. The price is for the hosting. It is on this page, not in the rooms.
  • Accounts per person. One login per house, shared by its phones. The portal cannot count people and does not try.
  • Scores. No points, no leaderboard, no "most helpful house". Counted reciprocity turns into debt.
  • Growth mechanics. No invite rewards, no streaks, no "your village is 60% set up".
  • Names in a push. "Somebody is away" rings the phones. Who, and until when, is behind the login.

Yours to ask for

  • A dues ledger. Who paid the water this quarter.
  • A duty roster with counts. Mowing, snow, the pump, and how many turns each house took.

Neither exists today, on purpose: the village that built the portal did not want them. The first village that asks gets one, as a setting with a default, and the default is off for everyone else. A village that turns it on is not running a fork; it is running the same portal with a different agreement, and the agreement is the village's to make.

Your land, drawn

Your village, drawn from your country's public cadastre: bring the file, or we draw it for you. Parcels from the cadastre, and where the terrain data exists, the streams and the ditches from a terrain model, so the map shows the water your village actually argues about.

One country today. For any other, ask us: where the cadastre is open data, we can usually get you there, and we say so before you pay.

Your data

  • Nightly backups, kept beside the village.
  • One-click full export. One file with everything, from the Houses room, any day, by the steward.
  • Published source. The portal is source-available under the Business Source License 1.1: free to run yourself for one village of up to ten houses, and every version becomes AGPL four years after its release.
  • Leave whenever and take everything. The export runs, the container stops, the data is returned. Nothing is held.

The price

Self-host

Free, forever

  • The image, a compose file, the docs.
  • Up to ten houses.
  • No support, no promises. The demo and the docs are the help.

Hosted

€15 a month

  • Per village. Every house included.
  • Your own container on your own subdomain, with TLS.
  • Nightly backups, updates, and a person to email who answers within 48 hours.

Your map, drawn for you: €250–450, once. The cadastre import for your land, the water where the data exists, your codex imported, crests for your houses, and an hour on a call with your founding steward. The price depends on the country's data.

Sovereign: €45 a month. Your own virtual machine in a country you pick, off-site backups you hold, a signed data agreement, and a support commitment. For federations and for a village whose constitution asks for it.

No card to try it. Walk through the demo first.

The village that made it

I built Porta Pagi for my own hamlet: a handful of houses in a karst valley in Slovenia, which runs it today. Each room does one job the group chat did worse.

  • The Watchtower: "we are away, please watch the land", with dates, a watcher and a thread. The room the whole thing exists for.
  • The Market: "going to the shop, anyone need anything?" as a list with states, not a scroll.
  • The Tool shed: who lends what and who holds it now, so the question is looked up, not asked.
  • The Campground: who noticed a camper and who has the money, so everyone hears a claim and nobody collects twice.
  • The Codex: the text a house signs before it joins, kept where it is read.
  • Nothing counted: no tallies, no scores. That one is mine, and I would build it the same way again.

My village is not on this page. Its map is its own, and a picture of crests on real parcels is a map of who lives where. Every picture here is from the demo village.

Questions

Does it ring on an iPhone?
Yes, once the portal is installed to the home screen (Share, then Add to Home Screen; iOS 16.4 or later). A banner at the top shows that step on an iPhone, and once installed, offers the notifications.
Which languages?
English, Slovenian and Portuguese today. A village picks its own, and its houses switch between them. A new language is one dictionary file; we add one when a village asks.
Is it an app?
It installs from the browser and behaves like one: an icon on the home screen, notifications. There is no app-store listing, on purpose. Nothing between your village and its portal decides what you may run.
What happens if we stop paying?
The export runs, you receive it, the container stops. Your data is returned, not held.
Where is our data, and under what terms?
A hosted village runs in its own container, on a server we run, and only that village's houses can read what is in it. The written terms — the privacy note, the data agreement, what is kept and for how long — are being finished with a lawyer and will be on this page before the first hosted village pays. We would rather say that than pretend.
Who runs it?
One person, who lives in the village that built it, and answers within 48 hours. When an answer needs more hands, more hands are brought in.
Can we self-host and still ask for help?
The docs and the demo are the help for a self-hosted village. Email is for hosted ones. If you outgrow ten houses, or want to host it for others, write to us about a licence.