GairCor Technologies

Productivity · Personal & Business

Software worth keeping on your home screen.

GairCor Technologies builds enterprise-grade software across productivity and personal & business — with row-level security on every table, edge deployment, and a one-way data path that never points back out. Browse the hub and take what is useful.

Browse the App HubOr book a call

What we build

Mechanisms

Signed download link300s

Expires, then re-issued

Public read of the ledger0 rows

How it’s built

Public surfaceOpen intake
One-way only
Internal ledgerNever exposed outward
  • Row-level security on every table
  • Internal data never exposes outward
  • Edge-deployed

The flagship · Smart Money Management

GairCor Flow is live — and open to the public.

LivePublic launch · Personal finance and household budgeting

Consumer finance reimagined. Track spending, set budgets, and gain AI-powered insights into your financial health. Delivery is product-led: the way in is the product itself, not a sales call. Underneath it is the same foundation as everything else we ship — Supabase Postgres with edge functions, row-level security on every table, and audit logging on privileged actions.

What it does

  • 01Budget tracking and spend visibility
  • 02AI-assisted financial insights
  • 03Simple workflows for personal and small business use
Open GairCor Flow (opens in a new tab)Read the full details
Overview
Everyday accountSample

$4,820.55

Placeholder balance for a fictional household.

Spend, last six periods
  • Grocery marketEveryday−$64.20
  • Payroll depositIncome+$1,240.00
  • UtilitiesBills−$118.40
Illustrative interface concept — not a screenshot. Figures shown are sample data.

Engagements

Some work is delivered, not downloaded.

The work below has no install button, and that is deliberate. It is scoped with you before anything is built, which is why the entry point is a call rather than a download.

Looking for something you can use today? Browse the rest of the catalog in the App Hub.

  • Internal/External Portal

    One-Way Secure Portal System

    Delivered as
    Implementation service
    Availability
    Consultation-led
    Best suited to
    Operations teams and secure intake workflows

    Dual-layer architecture: a public website funnels data ONE-WAY into an internal ledger. Internal data never exposes outward.

    • Public-to-internal one-way intake design
    • Protected internal review surfaces
    • Audit-friendly operational workflows
    Book a call about Internal/External PortalScope first, then build.

Architecture

One way in. No way back out.

Every GairCor portal is split in two. A public tier takes input from anyone; an internal tier holds the record. Data crosses from public to internal and never the other direction — and that direction is enforced by the database itself, not by a rule in the application that someone has to remember.

Public tier

Marketing siteStatic export, served from the CDN edge
App HubPublic intake forms
Trust boundaryCrossed by policy, not by request

InsertPermitted

SelectNo policy grants it

Internal tier

Internal ledgerRow-level security on every table
Ops surfacesAudit-logged privileged actions
Internal/External Portal — One-Way Secure Portal SystemConsultation-led · Implementation serviceSupabase Postgres · Edge functions · CDN edge

How the boundary holds

  1. 01

    The database decides, not the application

    Row-level security is enabled on every table across the public and operations schemas. Access is resolved by Postgres on each query rather than by application code that could be skipped.

  2. 02

    Public writes in. Nothing reads back out.

    Public forms insert into the funnel. No public role holds a policy that can select out of the internal ledger, so the return path does not exist to be misconfigured.

  3. 03

    Downloads are signed and they expire

    Files are never handed out as public paths. Each download is issued as a signed URL that stops working 300 seconds after it was requested.

  4. 04

    Privileged actions leave a record

    Work done inside the operations layer writes to an audit log — the actor, the action, the record it touched, and when it happened.

See the Internal/External Portal

The boundary, demonstrated

psqlanonymous session
> select * from public.leads limit 5;(0 rows)-- rls on, no select policy: rows are never disclosed > insert into public.leads (email) values ('a@b.co');ERROR:  new row violates row-level security policy for table "leads"
Real behaviour of public.leads. Row-level security is on and no policy grants access to anon or authenticated, so a read returns nothing rather than an error — the table never even admits a row exists. Writes reach it only through the intake function, on the service role.

Start here

Go see if it’s worth keeping.

That is the whole pitch. The apps are in the hub — open one and decide for yourself whether it earns the space.

Browse the App HubBook a call instead