Why BorderKit

Preparation is a loop, not a packing list.

I spent years rebuilding setups from memory and scattered lists. Each use taught me something, and the next plan still started from fragments.

BorderKit is the correction: a record instead of a list: what I own, what a purpose requires, what actually went in the bag, and what that taught me.

The preparation loop

Each use should improve the next plan.

Plan

Set out what the situation requires.

PowerAdaptersCables

Use

Pack and use the setup in a real event.

3 / 4

Review

Record what earned its place and what did not.

Kept × 3Waived × 1

Refine

Carry that context into the next plan.

Cycle 04 opens with
3 categories · 1 swap

Without it

Every event starts from nothing

The knowledge exists: in a note, a spreadsheet, or your head. It just does not survive to the next event.

01
You own more than you can recall
Weight, location, and condition live in three different places, none of them current.
02
The same kit gets rebuilt every time
A list written for one trip is not reusable, so the next one starts from memory.
03
What happened is never recorded
The item that was dead weight goes back in the bag, because nothing captured that it was.

Scattered preparation: notebook, spreadsheet, half-packed gear on a dark surface

Who it helps

People who depend on their gear

Expedition crews, field teams, nomads, hobbyists who own a lot and remember less than they think.

You use the same gear across different situations, and each one needs a different subset.
Your plans repeat with variations: climate, duration, how many people you are packing for.
You are the person who gets asked what to bring, and you would rather answer from a record.

Field team checking gear before departure: cool, desaturated, documentary

A full inventory is not the entry fee. A plan can begin with the categories a situation requires, then link exact owned items only where they matter.

How I am making it

One person, working in the open

I am building BorderKit because I needed it, and I am building it deliberately. Capabilities are described as they work today; the Notes record the decisions worth recording.

Deliberate: Four primitives, modelled properly, before any surface gets decorated.
In the open: Releases are published as they ship, in the Notes, with the fixes included.
Honest limits: What is missing is named. Nothing planned is written in the present tense.

Working surface: laptop, notebook, gear being catalogued

One person also means a narrower roadmap and a slower release cadence. That is the trade I have chosen, and I would rather state it than have you discover it later.

I bring almost twenty years of professional software development and a postgraduate background in business analytics to how BorderKit gets designed, built, and supported.

Stated plainly

What BorderKit is not

Capabilities are described as they work today, not as they are planned. The same applies to the things I have decided against.

Not a marketplace. BorderKit never sells you gear or takes a cut of what you buy.

Not a social network. There is no feed, and your inventory is not published anywhere.

Not a lock-in. A portable JSON export of everything is available at any time.

Not an offline-first database. You sign in and load data once; the core workflow then keeps working offline.

Sound like the tool you have been keeping in a spreadsheet?

Join the beta list

Join the beta list.

One email when beta access opens, and nothing else. Notes remain available without an email subscription.