The platform for business software.
A verified operator builds the system. The platform runs everything underneath it.
The platform where an operator and a business build together.
Every business owner now has access to the same models. What they rarely have is the layer between an intention and a working system: what to build, in what order, what to leave out, and how to shape data so it survives a real week of work.
Operators carry that layer. They know a domain — manufacturing, clinics, logistics, professional services — and they are fluent enough with AI to have already put a live product in front of real users.
Wildmind verifies them, assigns them, and provides everything underneath: hosting, database, security, backups, versions, and the AI that stays inside the finished product.
From assignment to a second version.
The same sequence every time, whatever the trade. Each step is visible to both sides.
Assignment
WILDMINDA business joining the queue is matched with an operator whose domain fits the work, along with £10 of credit to build the first version.
Build
OPERATORThe operator opens an address — name.wildmind.com — and builds the system there, with an introduction page explaining what it is.
Sign-off
OPERATORWhen the system stands on its own, the operator signs it off. Wildmind tells the business what was built, by whom, and where to open it.
Use and notes
BUSINESSThe owner uses it and leaves a note on the exact place that bothers them — attached to the screen, the section and the version it was left on.
To-do and change
OPERATOREvery note lands as a to-do. The operator decides what belongs in the next version and builds it.
Version released
OPERATOR → BUSINESSMarking a version done tells the business it is live. Versions are switchable, and notes stay attached to the version they were made on.
The bill is what the system consumes. There is nothing else to buy.
No package to choose, no seats to count, no feature held behind a plan. A system uses AI, runtime and storage; that is the bill, and it is visible inside the product every day.
At this rate, about 68 days. The estimate moves as the system grows.
Two ways to be certain.
One number, every month.
Set from the first month of real usage. Overruns are the platform’s, not the business’s.
A limit that holds.
Name a monthly maximum. Reported on approach, never exceeded.
Never switched off.
At a limit or a zero balance, records, screens and export keep working. Only new AI answers pause.
How that is enforced.
Three things a business never has to arrange for itself.
Every business has an operator
An app does not start without one. That is a condition of the platform, not something to negotiate — which is why places open in small numbers rather than all at once.
The operator answers to Wildmind
Verified before assignment, and covered afterwards. If one steps away, another takes the desk with the full history in front of them. No business is left holding a system nobody knows.
The system stays up
Records, screens and data keep working regardless of balance, limit or dispute. Nothing a business depends on is used as leverage.
An operator on the work, at nothing like the price of a project.
Custom software has always meant a development budget. It does not here, and the reason is worth stating plainly rather than hiding in a plan.
Pays for what runs, plus one agreed figure for the operator.
Nothing is bought up front and no development budget is raised. The infrastructure is already built and shared across every system on the platform, so what a business funds is its own running cost and its operator’s time — not a company’s overheads.
Earns from several businesses, not one large project.
AI compresses the building; judgement is what takes the hours. One operator can therefore hold a handful of systems at once, and their income is the sum of them. Wildmind supplies the platform, the matched businesses and everything under the software, so their time goes into the work rather than the plumbing.
Is penalised for stopping.
No lock-in, no notice period, no exit fee, no feature switched off to make a point. A business that leaves takes its system and its data; an operator who steps away is replaced by another with the full history in front of them.
No system starts without one, and the terms are their own.
Every system on Wildmind has an operator assigned to it. A business cannot start one without an operator, and cannot be left without one afterwards — that is a rule of the platform, which is why places are released in batches rather than all at once.
The first version is built and signed off before any fee is discussed. From there, the scope and terms of the engagement are agreed directly between the business and its operator, the way professional work is normally engaged.
Wildmind does not set that rate, take a commission on it, or invoice for it. The platform bill is separate and covers only what running the system costs.
Stated in full, because a business cannot audit what it cannot see.
Software built here inherits the whole arrangement below. None of it is optional, and none of it is charged for separately.
The providers behind this stack are named to each business in its own system documentation once the software is built — where the detail is verifiable — rather than used as decoration on a marketing page.
Facility
- ISO/IEC 27001 certified data centre operations
- Staffed 24/7, video surveillance, electronic access control with biometric verification
- Visitor logging and escorted access; no unaccompanied entry to server rooms
- Early smoke detection with gas-based suppression
Power and network
- Redundant utility feeds, UPS and on-site diesel generators (N+1)
- Multiple carriers with independent paths; no single upstream
- Always-on DDoS mitigation at the network edge, automatic and unmetered
Host
- Dedicated CPU cores, ECC memory, NVMe SSD in RAID
- Hardened Linux LTS, unattended security updates
- Firewall restricted to 22 / 80 / 443; key-only SSH, password authentication disabled
- Automated banning of repeated authentication failures
Application
- Container isolation per service; one database per business, never shared tables
- Secrets held outside the codebase, injected at runtime
- Least-privilege database roles; parameterised queries only
- Row-level authorisation checked server-side, not in the interface
Cryptography
- TLS 1.3 with modern cipher suites, HSTS, certificates issued and renewed automatically
- AES-256 at rest on volumes and on every backup copy
- Credentials stored as salted hashes; tokens held in an encrypted vault
Continuity
- Nightly full backup, seven-day point-in-time restore, kept on separate storage
- Restores exercised, not assumed
- Uptime, database latency and backup age monitored continuously and shown in the product
- Versioned releases with single-command rollback; data survives a rollback untouched
The system that starts small is the system that grows.
Capacity is added underneath a running system. There is no second product to migrate to, and no rebuild at the point it starts to matter.
Vertical
- Cores, memory and storage increased on the running host in minutes
- Database tuned to the new profile rather than left at defaults
Horizontal
- Read replicas for reporting so analysis never slows the working day
- Background workers for imports, exports and scheduled runs
- Static assets served from cache at the edge
Data
- Indexed from the first version; query plans reviewed as volume grows
- Partitioning and archival introduced before tables become a problem
People
- Three users or eighty on the same system, with roles and permissions rather than separate installs
- Second and third sites added as data, not as another deployment
What is held, where it sits, and who is able to read it.
Written the way it would have to stand up in a data request, not the way it reads best.
Held
- The business records the system exists for
- Conversations with the assistant, and the screen they were asked from
- Notes, with the screen, section and version they were left on
- Usage events — which screen, which action — and the sign-in email with the timestamp of consent
Never collected
- Card or bank details — payment is handled by a regulated processor, and the platform never sees the numbers
- Location, advertising identifiers, third-party analytics or ad-network tags
Residency
- The region is decided for each system by the business and its operator, not fixed by the platform — several are available, and the one in use is named in that system’s own documentation
- Backups are held in the same region as the records they copy
- An EU region keeps the whole system inside GDPR jurisdiction; that is the default unless there is a reason to choose otherwise
- Content sent for an AI answer is processed by the model provider, which may sit outside that region; the provider is named in each system’s own terms
Read by
- Conversations and notes are readable by the platform team to improve the product, and that is stated inside the product rather than buried here
- Business records are opened only to resolve a technical fault, and the access is logged
- Nothing is sold, shared or used to train a public model
Rights
- A full copy on request, in a format another team can load
- Correction, deletion, and export at any time — deletion propagates through backups within the seven-day window
- Stopping is immediate and costs nothing; the system and its data leave with the business
Sub-processors
- Every provider that touches data is listed by name, with its role and country, in the system’s own terms document
- That list changing raises its version number and asks for consent again at sign-in
The same assistant, in a pocket.
Everything the panel does inside the product — answering on the screen in front of it, taking notes, showing what the system has spent — on a phone, for the days nobody is at a desk.
iOS and Android · after batch 02ORD-2841 · Brekke Nordic — awaiting approval
The next batch opens 4 September 2026.
Places are released in batches so that every business admitted has an operator on it from day one. Batch 01 is full and closed to new starts.
Join the waitlist
An app does not start without an operator, so intake follows the batches. Batch 02 opens 4 September 2026, and the list is worked through in the order it was joined.