The content platform behind client websites — built on one uncompromising idea: the data belongs to the people it’s about.
EasySiteControl is built by FutureGen Systems and grew out of running real client websites. The first version did what every CMS does: it held the content, served the APIs, and quietly made itself very hard to leave.
The current platform is a ground-up rebuild around a different contract. Each client workspace lives on its own subdomain, and every project connects to a MongoDB the client owns — we keep only what routing requires, and publish exactly what that is. If we disappeared tomorrow, our clients’ content would still be sitting in their own databases, in plain collections, ready to use.
From that foundation the platform grew upward: schemas with enforced validation, generated records APIs, media in the client’s own bucket, end-user sign-in — and most recently, custom API endpoints and automations built as visual flows, so a site can have real backend logic without anyone writing server code.
Every project connects to a MongoDB the client supplies. Content, files and users live there — not on our side. Leaving is pointing your apps at your own database.
Required fields, unique values and relations are enforced by the server — uniqueness is backed by real database indexes, and every edit writes a history entry.
Members with scoped roles, API keys with exact permission lists, and a clean split between your team and your site's own signed-in users.
Generated records APIs come free with every schema, and custom endpoints and automations are assembled on a visual canvas — tested, logged, and rate-limited.
Claims about data ownership are cheap, so the platform documents its own data handling: every collection we keep and every collection that stays in your database is listed publicly, and the product’s release notes record what changed in every version.