Indigenous governments

// The problem

An administration keeps its membership list, program enrolments and contact details in separate spreadsheets, and community notices go out by posters, a social media page and phone calls.

// What we would build

A membership and administration system the Nation hosts on its own server, with access to sensitive records approved through the Nation's own governance, program enrolment for staff, and a community app for notices and updates in English and the Nation's language. The data stays where the Nation decides, following the OCAP principles.

// What is in it

// Stack

• Next.js
• React Native
• PostgreSQL
• Server owned by the Nation
• Encrypted backups

// The problem

A housing department tracks units, the waitlist and repair requests on paper and in spreadsheets, and maintenance staff in outlying areas cannot see the request history for a home.

// What we would build

A housing system for units, tenancies, the waitlist and inspections, with an iOS and Android app maintenance staff use offline, and rent charges posted to QuickBooks Online, built on the QuickBooks Online API.

// What is in it

// Stack

• Next.js
• React Native
• PostgreSQL
• QuickBooks Online API
• AWS Canada

// The problem

A lands department receives permit and consultation referrals by email from several ministries and companies, each with a deadline, and tracks them in a spreadsheet one person understands.

// What we would build

A web system that logs every referral with its deadline, area and documents, routes it to the right staff and committee, records the Nation's response, and keeps sensitive site information behind access rules the Nation sets.

// What is in it

// Stack

• Next.js
• PostgreSQL with PostGIS
• S3-compatible storage
• AWS Canada

// The problem

Program staff spend days each quarter rebuilding the same participation and spending figures in a different template for each funder.

// What we would build

A reporting workspace that builds each funder's figures from program records, and an assistant on an open-source model running on a server the Nation owns that prepares narrative sections from the Nation's own records for staff to edit and approve. No community data leaves the Nation's server.

// What is in it

// Stack

• Llama or Mistral (open-source)
• vLLM
• PostgreSQL with pgvector
• Next.js
• Lenovo GPU server owned by the Nation

// The problem

A Nation issues its own membership cards on plastic, and partners who need to check membership for a program or discount have to phone the office.

// What we would build

Digital cards issued by the Nation as verifiable credentials that members hold in a wallet app, with the Nation alone able to issue and revoke them, and a private ledger holding only the Nation's public keys and revocation list. A signed card with a lookup service often does the job; the ledger helps when several Nations or partners verify each other's cards.

// What is in it

// Stack

• W3C Verifiable Credentials
• Hyperledger Indy or Besu (private, permissioned)
• React Native
• Next.js
• AWS Canada

// The problem

A Nation's membership, housing and program systems sit on an office server and a few cloud accounts set up by different contractors, and nobody is sure where the backups are or who still has access.

// What we would build

One managed home for the community's systems in Canadian regions, set up as code, with access reviewed against a list the Nation approves, backups restored in a test every month, and a plain monthly report on what we ran, changed and found.

// What is in it

// Stack

• Terraform
• PostgreSQL
• Grafana
• Restic
• AWS Canada