Custom software. Practical AI. You stay in control.
We build websites and custom software that make everyday work easier. We can also set up AI to run on your own computers. We check updates for quality and security, and a person approves changes to your software before they’re released.
Try something we made.
Midnight / 01
A 3D cassette player in your browser. We created all the music ourselves, combining AI tools with our own creativity.
Turn it, choose a track and press Play. Opening the lid pauses playback. Music starts only when you press Play.
What we build
Find information faster
Search council meeting records, agendas and video, with links to the original sources so you can check what you find.
A safer place to test AI
Try AI tasks in a separate working space, with activity records, spending limits and controls on internet access.
Help building software
Turn a written request into a proposed software update, with checks, a second review and human approval before changes reach the software you use. We explain any project limits before work starts.
Work with legal documents
Extract text and check references in legal PDFs on your own computer. We explain accuracy limits so you know what still needs a person’s review.
Apps designed for phones
Private web apps for your work, with a login and a place to keep your data. We check the screens at phone size before release.
Help with customer replies
Prepare reply drafts for you to review and send. We test sending in a practice setup before live sending is approved.
AI on your own computers
Run AI for text and images on hardware you control. We measure speed and memory use to help you understand what the setup can handle.
Hardware prototypes
Explore ideas for small electronic devices, with a bench for testing programmable boards and recording what works.
Websites for your business
Clear, useful websites with the hosting and domain kept in your name. Public pages stay readable even when scripts are turned off.
See what is changing and why.
Before you approve an update, you get a short summary: what you asked for, what will change, what was checked and any risks. We explain the important points in everyday language, with the code and check results available for a closer look.
- Green small wording and documentation updates
- Yellow changes to the software
- Red changes to access, security or how software is released
Example update summary
- Your request
- Add our email address to the bottom of the website
- What we will check
The address is correct and clickable.
The page fits a phone screen.
- What will change
- Website contact details and page layout
- Risk level
- Yellow software change
Example update
- Request
- Add our email address to the website
- Risk level
- Yellow
From idea to approved update.
Here is how we handle changes to working software. Open a step to read more.
Five steps. Scroll or tab down to follow the example update.
-
Request: Add our email address to the website
Risk level: Yellow
Plan We agree what you need and what a successful result should look like before building. Step 1Plan
We write down what the software should do and how we will check it. Unclear requests go back for clarification.
A written requirement is a starting point. The review also needs to show which checks actually ran.
-
Request: Add our email address to the website
Risk level: Yellow
Build We work on a separate copy, keeping unfinished changes away from the software you use. Step 2Build
We limit what the AI can access and how much a task can spend. The proposed change goes through our review process before it can reach the working software.
-
Request: Add our email address to the website
Risk level: Yellow
Check We check for known security problems and run the agreed software tests before approval. Step 3Checkexample update
The results show what passed, what failed and what could not be checked. Security checks can block a change when they find a serious problem or a possible exposed secret.
Changes to access or security settings need extra attention from the person reviewing them.
-
Request: Add our email address to the website
Risk level: Yellow
Review A second AI reviewer looks for mistakes in the proposed changes. Step 4Review
The reviewer uses a different AI provider from the one that wrote the code, and cannot change the work. It reviews the exact version proposed for approval.
AI review can miss mistakes. We also use software checks and human judgment.
-
Request: Add our email address to the website
Risk level: Yellow
Approve A person approves changes to the working software before they are released. Step 5Approve
Approval applies only to the exact change reviewed. If the code changes, it needs fresh checks and approval. Without approval, updates to the working software stay on hold.
Some projects can automatically approve a separate change that adds tests for the agreed requirements, after its checks pass. Changes to the working software still need human approval. We agree those rules before work begins.
This demo needs JavaScript. It changes no software and releases nothing.
What we agree before we start.
If your data needs to stay on your own computers, we explain which tools can support that. Some private or fully offline setups cannot use the review process shown above. We explain the options and limits before we quote.
Some tools only support certain projects. We confirm what is suitable for yours before work begins.
Tools you can explore.
We agree what success looks like before building.
We check the work and explain what the checks cannot prove.
We document what the software can do and where it falls short.
Public tools for software teams
unbloat
A tool that helps remove unused code and outdated project notes, with checks to help keep projects tidy. Its code, setup guide and limits are available on GitHub.
go-public
A guided process for preparing code for public release, including security checks and scanning for private information. Its guide explains what still needs manual review.
A private tool for searching documents on one computer, designed to work offline.
Tell us what you need.
Tell us what takes too much time, what you want to improve and who will use it. Let us know if data needs to stay on your own computers. We explain what we can build, what it would cost and any limits.