Cap. 01
Infrastructure & platform engineering
Hosting, deployment and control planes: hardened servers, reproducible builds, TLS and networking, backup and restore paths that are exercised rather than assumed.
01 — StudioMade in the European Union
Fewer things,built properly.
We design and build infrastructure and products — engineered for European data residency and documented well enough to hand over. Commissioned work runs on the same terms.
In market:Renvy — In developmentjust.locker — Beta
specus/ˈspe.kus/noun · Latin
- 1.a cave; a hollow in rock.
- 2.a shelter, formed by what was taken away.
Scroll to enter
02 — Capabilities
Cap. 02
Product design & build
Interface, architecture and implementation carried by the same people — from the first flow diagram to the release that runs in production, with the decisions written down.
Cap. 03
Commissioned work
Client engagements on the same terms as our own products: scoped deliverables, documented systems, and a handover that leaves the client able to operate what we built.
03 — How we work
Four rules, applied to every engagement — our own products included. They are what keeps the work calm, documented, and easy to hand over.
01
Scoped before started
We tell you plainly whether this is work we should take, and what the first documented deliverable would be, before anyone commits.
02
One change window a week
Requests are batched into a single window rather than handled ad hoc. It is slower on any given Tuesday and faster over a quarter, because nobody is context-switching.
03
Documented as we go
The handover documentation is a deliverable with a due date, not something written at the end if there is time.
04
Few clients at a time
Deliberately. When we are full we raise the price rather than take on more, because the alternative is doing everyone’s work badly.
03 — How we work
Four rules, applied to every engagement — our own products included. They are what keeps the work calm, documented, and easy to hand over.
Step 01 of 04
Scoped before started
We tell you plainly whether this is work we should take, and what the first documented deliverable would be, before anyone commits.
Step 02 of 04
One change window a week
Requests are batched into a single window rather than handled ad hoc. It is slower on any given Tuesday and faster over a quarter, because nobody is context-switching.
Step 03 of 04
Documented as we go
The handover documentation is a deliverable with a due date, not something written at the end if there is time.
Step 04 of 04
Few clients at a time
Deliberately. When we are full we raise the price rather than take on more, because the alternative is doing everyone’s work badly.
04 — Products
Ref.ProductState
P—01In development
Renvy
Rental management for property owners and teams: organise properties, tenants, leases, payments and documents in one place.
P—02Beta
just.locker
A self-hosted control plane and PaaS. It adopts your own servers over SSH, hardens them, and gives you deployments, networking, secrets, backups and billing on infrastructure you continue to own.
End of ledger — 2 products listed, nothing else in market.
05 — Engineering standards
Standard 01
Fail-closed by default
Builds from source are refused until an ephemeral rootless builder is available; no privileged BuildKit persists on the execution host.
Standard 02
Immutable releases
Images are published to a registry and referenced by digest; rollback restores the previous digest, never a rebuilt artefact.
Standard 03
Verified restore
Backups are encrypted with an authenticated manifest, and restore drills are run and dated before any production promotion.
Standard 04
Health-gated updates
The control plane updates itself behind preflight checks and a database backup, with automatic rollback when a health gate fails.
Standard 05
Written before built
Threat models, architecture decision records and security reviews are documented artefacts, not implied.
06 — Where it runs
Residency
Hosting region and provider access are documented for each deployment. European hosting is available when required; any external service is reviewed separately.
Privacy
GDPR-native architecture — data minimisation and deletion paths designed in, not bolted on.
Encryption
Encryption at rest and in transit across services and backups.
Regulation
EU AI Act considered by design, ahead of any feature that would fall under it.
07 — What you get
- 01
Running infrastructure, not a proposal document.
- 02
Your servers, your provider accounts, your domains — in your name from the first day.
- 03
The documentation needed to run it without us.
- 04
Everything handed over on request, at any time, without a conversation about it.
08 — Who this is for
For
- Teams that need infrastructure to outlive whoever set it up.
- Work with European data residency requirements.
- New projects that get built properly the first time.
Not for
- Anything that has to be live by Friday.
- On-call outside the agreed window.
- Migrating live production systems with critical uptime.
We take greenfield work only, and we would rather say so here than discover it together later.
09 — Questions
01
Who owns the code and the infrastructure?
You do, from day one. Nothing is held hostage.
02
Where does the data live?
Hosting locations and external providers are agreed for each project and documented before launch. A European hosting region alone does not describe every provider that may process data.
03
How is work priced?
A setup fee for onboarding and provisioning, then a fixed monthly for an agreed scope. No hourly billing and no surprise invoices.
04
How quickly do you respond?
Within the agreed window. Urgent production incidents are handled outside it; everything else waits for the window.
05
What happens if we stop working together?
You keep the servers, the accounts, the domains and the documentation, and we help with the transition.
10 — Contact
Tell us what needs to exist and what it has to survive. We will tell you plainly whether it is work we should take, and what the first documented deliverable would be.
What happens next
- 01Your message is read by a person. Nothing is scored, ranked or classified by a system.
- 02You get a plain answer by email: whether this is work we should take.
- 03If it is, we propose the first documented deliverable — in writing, before anyone commits.