A few of the questions that tend to come up when people are deciding whether Lighthouse is the right place
for their infrastructure and consultancy work.
Who is this actually for?
Small teams, independent consultants, modest software houses and small organisations who want their infrastructure
to be boringly reliable rather than theatrical. If you want clear ownership, privacy, and someone who will write things down,
you are in the right place.
Where are the servers?
The core infrastructure runs on reputable European providers with strong privacy postures and clear contracts.
Exact providers and locations are documented for you as part of your onboarding, so you know where things live.
Do you read my data?
No. We do not sit and browse customer repositories or storage. Operational access is used only when something
needs to be fixed or configured, and even then we aim to work at the system level rather than the “poke around
inside your content” level.
We do keep access logs and metadata as required for security and legal obligations, but not to build profiles or sell anything.
How do you handle illegal or unacceptable content?
Our storage and hosting are covered by a clear acceptable use policy. Certain types of content – including illegal material,
extremist content and pornography – are not permitted. If we receive a valid complaint or lawful request, we will act on it:
typically by suspending access to affected material and preserving evidence where required.
We are not a generic file dump service and do not offer “anything goes” storage.
What about backups and disaster recovery?
Backups are treated as a first-class citizen rather than an afterthought. For hosted services such as Forgejo and S3 storage,
we run encrypted, tested backups with off-site copies. As part of consultancy projects we also help you design – and document –
a recovery plan that does not rely on luck or one person’s memory.
What happens if you get hit by a bus?
A fair question, and one that a lot of providers dodge. Our aim is that if Lighthouse vanished tomorrow, you would still
have the information and access you need to move on: repositories can be exported, backups are documented, and we can
provide guidance on how to migrate to another provider if needed.
Dependency is inevitable; lock-in is optional. We design for the former and avoid the latter.
What sort of support can I expect?
For hosted services we provide support via email, with sensible response times during UK daytime hours. For consultancy work,
availability and contact routes are agreed as part of the engagement. We do not run a 24/7 call centre, but we are serious
about responding and keeping you informed.
Do you have formal SLAs?
For larger or more critical engagements, we can agree simple written service levels – within the bounds of what a small,
independent company can reasonably honour. For most smaller clients, a clear understanding of expectations and good communication
are more effective than rigid SLA language.
How do I pay?
Regular hosted services such as Forgejo are billed via PayPal subscriptions on a monthly or annual basis. Consultancy work is
usually invoiced on completion of milestones or at agreed intervals. There are no hidden charges or unexpected extras.
Can I leave if it does not work out?
Yes. If you decide Lighthouse is not for you, we will help you export what matters – repositories, configuration notes,
documentation and, where applicable, stored artefacts. You should not feel trapped in order to keep your data safe.
Do you only work with open-source tools?
We favour open-source where it makes sense, particularly for infrastructure and core tooling, because it supports transparency,
portability and long-term maintainability. That said, we are pragmatic: if a proprietary service is the right tool for a job,
we will say so.
Is this the same company as the Haunted Lighthouse website and Mastodon instance?
Yes. The consultancy suite sits within The Haunted Lighthouse Limited and shares the same infrastructure, branding and
underlying principles. You are not being passed off to a separate organisation or white-label provider.