The digital foundation
your business actually owns.
Domain, email, website, security and backups — designed as one system, registered in your name, and documented well enough that you could hand the whole thing to someone else tomorrow.
Month to month, no lock-in. Australian entity, Australian hosting.
What this practice does, and the frameworks behind it
- Enterprise architectureTarget state, roadmaps and governance, aligned to the TOGAF 10 framework
- Solution and cloud architectureWell-Architected designs, built and run in Australian regions
- Delivery leadershipSenior-led delivery, from scoping through to handover
Built with
- AWS
- TypeScript
- React
- Node.js
- Git
- Java
- Python
- Spring
- Docker
- PostgreSQL
- Oracle
What we set up
Four things, arranged so they hold each other up
Sold separately these are commodities — a registrar will rent you email for five dollars a month. The value is not in the parts. It is in them being chosen together, configured to match how the business runs, and written down.
Domain and email that behave
Most small-business email trouble is not an email problem. It is a DNS problem, built in on the day somebody registered the domain in a hurry and pointed the records wherever was quickest.
- Your domain registered in your name, with the registrar account under your control
- SPF, DKIM and DMARC configured, so your mail reaches the inbox instead of the spam folder
- Mailboxes, aliases and forwarding arranged around how the business actually works
The result is boring, which is the entire point. Mail arrives, mail sends, and nobody has to think about it again.
A website you can edit and keep
A website is only an asset if you can change it and take it with you. A surprising number of small businesses find out, years in, that they can do neither.
- Built for your business rather than adapted from a template with your logo dropped in
- Hosted in Australia, on infrastructure in your account — not resold to you through ours
- A plain editor for the things that change: hours, prices, people, photographs
If you leave, you take the domain, the hosting, the content and the credentials with you. That is agreed in writing before any work starts.
Security, backups, and a written handover
The subscription web agencies you will be comparing us against sell a firewall and nightly backups as the reason to move up to the middle package. Those are not features. They are the floor, and charging for the floor is how the category ended up where it is.
- Multi-factor authentication on every account, and a password manager that belongs to you
- Automated backups with a restore that has actually been performed, not merely scheduled
- A handover document listing every account, what it does, and who controls it
The day you change providers, sell the business, or need to recover an account, that document is the difference between an afternoon and a fortnight.
How we work
We look at the business before we look at the website.
Enterprise architecture is, stripped of the vocabulary, the practice of understanding how an organisation works and then designing the systems to match — rather than buying software and reshaping the organisation around it. That is a useful thing to do for a company of five as well as a company of five thousand. It has simply never been affordable at this end of the market.
- TOGAF 10 Foundation
- Enterprise architecture practised at large-organisation scale, applied to a business of five people.
- You own every account
- Domain, hosting, email, analytics — registered in your name and handed over with credentials and documentation.
- Month to month
- No twelve-month minimum. Leave when you like and take everything you arrived with.
- Senior-led, no junior bench
- You deal with the person doing the work. That is a real constraint on how many clients we take, and we would rather say so.
How it is built
The parts you cannot see are the ones that decide whether it lasts
Anything can be made to look finished. These are the decisions taken on every build, whether or not anyone asks — because they are expensive to add later and invisible until they are needed.
Security decided at the start, not bolted on
Zero trust: nothing is treated as safe because it sits inside the network. Every request proves who it is and what it is allowed to do, on its own merits.
Who can do what, written down
Role-based access control from the first day, so permissions follow the job rather than accumulating quietly over years. Joiners and leavers are a process, not a scramble.
Encrypted on the wire and on the disk
Data is encrypted in transit and at rest, with keys held by the platform’s key management rather than pasted into a configuration file somebody can read.
Every change leaves a trace
Audit trails, application logs and metrics collected from day one, with monitoring and alerts on the handful of things that genuinely warrant waking someone.
Built for the load it will really see
Performance targets are agreed before the build and measured against, rather than discovered by your customers on the busiest day of the year.
Room to grow without starting again
More people, more locations or more data should be a configuration change. Designs that only work at today’s size are the most common reason for a rebuild in year three.
Backups that have actually been restored
A backup nobody has restored is a hope. Recovery is rehearsed, and how much you could lose and how long it would take are written down before you need them.
Every account in your name
Domain, hosting, cloud and email registered to your business, with the credentials handed over. Nothing is held on your behalf, so leaving costs you nothing but notice.
TOGAF
Architecture that follows a framework, not a habit
Work is structured with TOGAF 10 — the enterprise architecture method large organisations run their transformations on — applied at the size of your business rather than in its full ceremonial form. It is why the questions asked in week one are the useful ones.
AWS
Built and run on AWS, in Australian regions
Applications, storage, databases and networking on AWS, following the Well-Architected Framework and deployed as code so an environment can be rebuilt rather than repaired. Hosted in Sydney or Melbourne by default, so your data stays in the country.
The other half of the practice
Architecture and cloud work, for organisations that need it
The same practitioner also takes enterprise engagements: target-state architecture, cloud strategy and migration assessment, modernisation and cost work. If you have arrived here from that direction, the detail is on its own page.
ARCHITECTURE & CLOUDBefore you ask
The questions we get asked first
A one-off setup fee for the design and configuration work, then a monthly subscription in AUD covering hosting, email, monitoring, backups, support and small changes. The setup fee is separate deliberately: the subscription agencies bury that work in the monthly price and recover it through a twelve-month minimum, which is why leaving early costs you. Full pricing, and an estimator that gives an indicative range in about a minute, is published on the pricing page.
Yes, all of them, and that is checkable rather than a promise. The domain is registered in your business name. Hosting, email and analytics accounts are created under your details and billed to you. At handover you receive every credential along with a written record of what each account is for. Nothing is held on your behalf.
No. The subscription runs month to month. The common arrangement in this market is a twelve-month minimum, and it exists to recover setup costs that were never priced openly. We price the setup openly instead, so there is nothing to lock you in for.
You already hold the accounts, so there is no migration to negotiate — you stop the subscription and everything keeps working. We provide an exit pack: the handover document brought up to date, a full backup of the site and its content, and a short call with whoever is taking over. The exit is written into the engagement before the work begins, not improvised at the end of it.
In Australian regions by default — ap-southeast-2 (Sydney) on AWS, australia-southeast1 on Google Cloud, or Azure Australia East, depending on what the workload needs. For most small businesses that is the whole answer. Where it is not, we classify the data first, decide what may leave the country and what may not, and put the resulting constraint in the contract rather than in a slide. We do not hold an IRAP assessment or any government certification, and we will say so plainly if that is what you need.
Usually as the person who defines how the pieces fit together, while your existing provider keeps running what they run. That works best when the boundary is explicit — who owns which account, who is called when something breaks, what changes need a conversation first. We write that boundary down at the start. Replacing an incumbent who is doing a reasonable job is rarely the recommendation.
GTSR Solutions is an Australian private company and invoices in AUD with the ABN shown — ABN 54 697 553 870, ACN 697 553 870. Engagements run on a short written services agreement covering scope, price, ownership of the accounts and assets, and how either side ends it. Payment terms are stated on the invoice. There is no offshore entity and no third party in the contracting chain.
Tell us what you have, and what is annoying you about it.
A short conversation is usually enough to say whether there is anything worth doing. If there is not, we will tell you that.