Skip to content
POLARGATE
Build // Your operations, out of the spreadsheet and into a real application.

Web apps and internal portals

Internal portals, back office apps and operating systems built on Supabase, with row level security, roles, audit logs and Microsoft single sign on. Fixed price for a first phase, senior led from discovery to launch.

A supervisor in a glass booth overlooks a bus depot at twilight, his monitor showing a vehicle list and route map, radios charging on the desk

What it is

An internal web application for the work your company actually runs on: the operations board, the back office, the client or supplier portal, the tool that today lives in a shared Excel and a chain of emails. Polargate builds it as a real application on Postgres, with named users, roles, permissions and a record of who changed what. It runs in the browser on any device, and it can be wrapped as an iOS and Android app when the work happens away from a desk.

How we do it

We start from your process, not from a template. In the Discovery Sprint we read the spreadsheets, the procedure documents and the email threads where the work is coordinated, and we turn them into a data model, a role map and a written scope for a first phase. Then we build. Security lives in the database: row level security enabled and forced on every table, roles as a Postgres enum checked by a function, sensitive fields such as commercial margin masked by role through a view, and an immutable audit log written by a trigger with an admin only viewer. People sign in through Microsoft Entra ID with the account they already have, or by email with a hardened password flow on your own domain. Every screen ships with its loading, empty and error states, keyboard access and 44 pixel touch targets. Before anything is handed over, the build goes through repeated adversarial audits: on the operating system we built for a hotel refurbishment contractor, one round produced 59 confirmed findings across bugs, security, interface and accessibility, all fixed before delivery.

What you get

A first phase in production with the modules that carry the most operational weight, running on your own Supabase project and your own repository, with no vendor lock in. You keep the schema, the migrations, the source code and the keys. Business day email alerts, file and photo upload, notifications, and an admin area for the people who govern the system. And a roadmap for the phases after this one, priced separately, so nobody signs a blank cheque.

What it costs

A first phase is fixed price, from 12,000 EUR, and typically lands between 12,000 and 25,000 EUR depending on the number of modules and integrations. It can be paid in six to ten monthly instalments by direct debit. The Discovery Sprint that precedes it is also fixed price, from 4,900 EUR, and half of it is credited against the build if it starts within 60 days. After launch, a Care retainer from 850 EUR per month covers senior maintenance and evolution.

Proof

FAQ

Questions, answered

How much does an internal portal or back office app cost?
A first phase with Polargate starts at 12,000 EUR fixed and usually lands between 12,000 and 25,000 EUR, depending on how many modules and integrations it carries. The price is closed before work starts, based on the written scope produced in the Discovery Sprint, which is itself fixed from 4,900 EUR with half credited against the build if it starts within 60 days. We do not bill by the hour, and the build can be spread over six to ten monthly instalments.
How long does it take to build an internal web app?
Expect a first testable version about a month after development starts, and a complete first phase in roughly eight effective weeks of work, which normally spans three to five calendar months. The calendar time depends mostly on your side: decisions, content and access to the people who know the process. We deploy to production continuously, so your team is using parts of the system long before the phase closes.
Can our employees log in with their Microsoft account?
Yes. Polargate connects the portal to Microsoft Entra ID, so people use the corporate account they already have and your own conditional access and offboarding rules apply. We have done this on a corporate employee portal whose directory of more than 10,000 active employees is synced from Microsoft Graph. Where Entra ID is not available, we set up email sign in with a hardened reset flow sent from your own domain.
How do you stop one department from seeing another department's data?
Permissions live in the database, not only in the interface. Every table has row level security enabled and forced, roles are a Postgres enum checked by a database function, and sensitive fields such as commercial margin are masked by role through a view. That means data cannot leak by calling the API directly or through a mistake in one screen. A trigger writes every change into an immutable audit log with the user behind it.
Do we own the system, or are we locked into your platform?
You own it. The application runs on your own Supabase project, your own repository and your own hosting account, and you receive the schema, the migrations, the source code and the keys. Polargate does not keep your data on a shared platform and charges no licence fee for software built for you. If you stop working with us, the system keeps running and another team can pick it up.
INITIATE

Start the engine

Tell us what you are building in a few short questions. A senior engineer answers in writing within 48 business hours, with a first take on scope, timeline and price.

Start your project Talk to us