Architecture & deployment
Size the hardware or the cloud, stand the stack up properly the first time, wire in TLS, single sign-on, and backups before anyone logs in.
Open source infrastructure, deployed and managed.
GLAT stands up the collaboration, communication, and data platforms your organization actually runs on — then keeps them patched, backed up, monitored, and answered for. No per-seat licensing. No lock-in. Your data stays yours.
- Hosting
- Your hardware or your cloud. On-premises, colo, or a provider you already pay — the stack travels.
- Licensing
- No per-seat tax. Add the twentieth user, or the two hundredth, without renegotiating a contract.
- Ownership
- Data and configs are yours. Documented, exportable, and handed over — including if we part ways.
- Nonprofits
- A core part of the practice. Small teams with real compliance and reporting obligations.
What we do
Four ways organizations bring us in.
Usually it starts with one and grows into the others. Every engagement ends with documentation your own team can work from.
Migration off SaaS
Move files, mail, chat history, and accounts across without a lost weekend — and without asking staff to learn everything at once.
Managed operations
Patching, version upgrades, backups with restores that are actually tested, uptime and capacity monitoring. One place to send the ticket.
Vendor-neutral advisory
What to self-host, what to keep buying, what to retire. Sometimes the right answer is a commercial product — we will tell you when it is.
The stack
Software we deploy and keep running.
Mature, widely deployed open source projects — chosen because they hold up in production and because you can hire someone else to work on them if you ever need to.
Collaboration & communications
Files, calendars, chat, meetings, and mail — hosted under your own domain instead of rented per head, per month.
- Nextcloud
- Mattermost
- Rocket.Chat
- Jitsi Meet
- Zulip
- Mailcow
- Mailu
Data & observability
The numbers your systems already produce, collected and put in front of the people who have to answer for them — staff, boards, and funders.
- PostgreSQL
- Grafana
- Prometheus
- Metabase
- n8n
- Home Assistant
Not on the list? Ask. If it is open source, well maintained, and a fit for what you are trying to do, it is worth a conversation.
How an engagement runs
Assess, deploy, operate.
In that order, and you can stop after any of them.
Assess
We inventory what you run today, what it costs, and where it hurts — then put a written plan in front of you with the trade-offs stated plainly. No obligation to continue.
Deploy
Build it in staging, migrate the data, cut over on a schedule that respects your calendar, and leave behind runbooks written for humans.
Operate
Ongoing patching, upgrades, backup verification, and monitoring — with a named person who picks up when something breaks.
Who we serve
Small teams carrying real infrastructure.
Nonprofits & foundations
Grant reporting, donor and case data, and staff collaboration — on budgets that cannot absorb a per-seat price increase every renewal.
Small businesses & manufacturers
Shop-floor and back-office systems that have to keep running, and data that should not leave the building just to be graphed.
Teams leaving expensive SaaS
Organizations that have outgrown their subscriptions and want a path off them that does not strand their people or their history.
Why open source
You own the data
It sits in systems you control, in formats you can read, on storage you can point at.
Cost scales with use, not headcount
Growth shows up as capacity planning, not as a renewal quote with a new number on it.
The exit stays open
Nothing here requires us. If you hire in-house or move on, the documentation goes with you.
Start here
Tell us what you are running now.
A short note about your organization, the systems you depend on, and what is not working is enough to get a useful answer back.
Contact@glat.io