← all posts

Websites, email and publishing for churches — from a publisher that runs its own

Publifye· ·4 min read ·Publifye AS ·publifye

For ten years we have published Bibles — first as TruthBeTold Ministry, since 2021 as Publifye AS in Oslo — and for ten years we have run every piece of the machinery underneath that work ourselves: the websites, the mail that has to arrive, the stores, the backups, the publishing pipeline that turns a manuscript into a typeset book. Over 4,200 Bible editions have gone through it.

Today we are opening that machinery to churches.

What this actually is

Most congregations do not have an IT department. They have a website somebody's nephew built in 2019, a mailing list that silently stopped delivering, and a shelf of sermon recordings nobody can find. None of that is a moral failing — it is what happens when infrastructure has no owner.

So that is the service: we become the owner of the boring parts. Concretely, the things we take on look like this:

  • A congregation website that is fast, readable on a phone, and editable by the people who actually update it — no deploy, no developer on call.
  • Email that reaches the inbox. Most church mail problems are not content problems; they are missing SPF, DKIM and DMARC records that quietly route the newsletter to spam. This is fixable, and provably so.
  • Sermon and teaching publishing — text, series, study material — on the same pipeline our own books go through.
  • Member sign-in and forms that do not leak data and do not depend on a volunteer's personal account.
  • Backups that are actually tried. A backup nobody has ever restored is a hope, not a backup.

Two rules shape all of it. First, everything is scoped and quoted — there is no plan to pick and no per-seat tier, because a twelve-person fellowship and a thousand-member church are not the same job, and pretending otherwise is how churches end up paying for software they use two percent of. Second, you own everything, throughout — the domain, the words, the images. If you ever leave, we hand over what we hold and help you move it.

If what you already have works, we will say so and leave it alone. Often the honest finding is that the website is fine and it is the mail records or the backups that need a week of attention.

The tools underneath are the ones we use ourselves

None of this was built for the occasion. It is the same estate our own publishing runs on:

  • Darash, our Scripture research engine — the Hebrew and the Greek, Strong's, morphology, cross-references — which your AI assistant can use directly.
  • Junifye, where a book, a study series or a sermon collection is written once and comes out as a web reader, an EPUB and a print-ready PDF.
  • Tringine, new and in beta: pick a translation, a scope — a whole Bible, a New Testament, the single book you are preaching through — and a trim size, and it builds you a print-ready PDF any print shop will accept. We do not run a press and never will; we hand you the file that presses accept.
  • The Bible store, where the 4,200+ editions live.

And those are only the presses with their names on the door. Underneath them run some thirty-seven services we built for ourselves, because our own publishing demanded them — and the core of that machinery is exactly what the church offering stands on. Lighthouse, where every reader, member and customer signs in once and is known everywhere — accounts, access and payments in one place. Pubhub, the authentication spine the services themselves trust each other through. Pubbin, so every deployment updates itself from a central registry and nobody logs in at midnight to ship a fix. Pubvol, backups taken on schedule to off-site storage and restore-tested, because an untried backup is a hope. Pubmail, the email machinery that watches its own sender reputation so the newsletter actually arrives. The rest of the estate — logging, analytics, the CDN, down to the service that files our own accounting — runs on the same pattern. We do not resell someone else's platform with our sticker on it: when we say we run the infrastructure, this is the infrastructure, and we are its heaviest user.

Everything we run can be hosted by us or installed on your own servers, and it keeps itself updated either way.

Where to start

The starting point is deliberately small: tell us what you have — your website address and a sentence about what worries you is enough. We will look and tell you what we found, including the parts that are fine and need nothing from us. "We do not really know what we need" is the normal case, not a problem.

The longer description of the work, with the questions churches ask before writing, is at publifye.com. Who we are, in full, is at publifye.org.