Skip to main content
MeetCost is a self-hosted meeting cost estimator for Google Meet, Zoom, and Microsoft Teams. It calculates the real payroll cost of meetings in real time — at scheduling, after the meeting, and in periodic team digests — all running on your own infrastructure with salary data encrypted under a key only you hold.

Quickstart

Get MeetCost running locally in under 15 minutes with a live cost estimate.

Deployment

Deploy to Docker Compose or Kubernetes with Helm for a production-grade setup.

API Reference

Integrate MeetCost with your scheduling tools using the REST API.

Privacy & Security

Understand exactly what data MeetCost holds and what it transmits.

​
Why MeetCost?

A recurring 8-person weekly sync feels free at the point of scheduling. It is not — it is roughly £40,000 a year of payroll. Every tool that shows you this number is SaaS, which means shipping salary data to a third-party cloud. MeetCost is the same idea, self-hosted: the calculation runs on your infrastructure, against your database, under your encryption key.

Scheduling Estimates

See the cost and annualised total as you build the invite list.

Post-Meeting Summaries

Actual cost from actual attendance — not what was booked.

Team Digests

Weekly and monthly spend reports by team, with CSV export.

Pay Data Encryption

AES-256-GCM under a key you supply. No key escrow, no vendor access.

Role-Based Access

Granular disclosure controls that prevent salary inference.

Adapter System

Extensible adapters for directories, attendance, and HRIS systems.

​
How it works

Three thin clients — a Google Meet add-on, a Zoom app, and a Teams app — talk exclusively to your MeetCost backend over HTTPS on your own domain. Pay data never reaches the client. Every cost response is redacted server-side for the specific viewer before it leaves the service.

​
Get started

1

Clone and configure

Clone the repository and copy the example environment file.
2

Generate an encryption key

MeetCost encrypts every pay figure with a key you supply. Generate one now and paste it into .env.
3

Start the service and seed demo data

4

Open the admin console

Visit http://localhost:8000/admin, click Get a development token with ada@example.com, and you’re in. Try the /api/v1/estimate endpoint to see a live cost estimate.
The Docker Compose setup uses development auth and SQLite. See Deployment for a production-grade setup with Postgres and OIDC.