Work we take on, and the assembled stacks for teams.
70 answers
Filters the questions below as you type. To search every topic, go back to the support index.
Try a shorter word, or send it to us — an answer nobody could find is a question we have not written down yet.
It is genuinely included, and the quote shows you the build cost on its own so you can compare it against anyone else. What we get out of it is a site running on infrastructure we control — which is also why we can promise it will be fast.
More on Website design
The domain and the hosting renew at the standard rates published on this site. Not an agency rate, not a rate that appears once you are committed — the same figures anybody reading the catalogue pays.
More on Website design
The honest answer is that it depends on how quickly the content arrives, because that is what actually holds most projects up. Your quote carries a real timeline for your scope, and it is a commitment rather than an estimate we quietly revise later.
More on Website design
Yes, and we set it up so that the parts you will want to change are the parts you can change, without being able to break the layout by accident. We hand over the access and show you how it works.
More on Website design
No, and it is usually an advantage — we can see what works and what your visitors already do. We move you across without the old site going dark in between, and existing addresses keep working.
More on Website design
Keeping the software current, taking and testing backups, renewing certificates, watching that the site is up, and the small changes a real business needs — a price, a phone number, a new page. A redesign is a new project and we will say so rather than let it drift.
More on Website design
You do, all of it: the domain, the content and the site. We hand it over and help you move it. There is no clause anywhere that makes leaving expensive, because a client who stays only because leaving is hard is not a reference.
More on Website design
No, and most of the sites we look after were built by somebody else. We do not need the original developer, their files or their goodwill — access to the site and the hosting is enough to start.
More on Security & maintenance
No. We work on the hosting you already have, including hosting we do not sell and cannot see the inside of. If moving would genuinely fix something we will say so and explain what, but it is never a condition of the work.
More on Security & maintenance
Not from this page, and neither can anybody else — a score on a marketing page is a guess dressed up as a measurement. What we can do is look at the actual site and send you what we found, item by item, with what each one would take to fix. That review costs nothing and you can act on it without us.
More on Security & maintenance
Almost never. The usual outcome is a site back online the same day or the next, cleaned at the source rather than patched over, with the way in closed so it does not happen again in a fortnight. The cases that take longer are the ones with no usable backup and a compromise that has been sitting there for months — and those are still recoverable, they just cost more time.
More on Security & maintenance
Usually not. Most of the work happens on a copy, and the live site only goes to a holding page if it is actively harming visitors — serving malware, sending mail in your name, or carrying a browser warning that is costing you more than an hour of downtime would.
More on Security & maintenance
Because we restore one, on a schedule, to somewhere that is not your live site, and the date of the last successful restore is in the note you get. An untested backup is a hypothesis, and the day you find out is the worst possible day to find out.
More on Security & maintenance
Updates are applied to a copy first and looked at by a person before they reach anybody's customers, and a restore point is taken before the live site is touched. When something does break — it happens, and anybody who tells you otherwise has not done this long — putting it back is minutes, and then we find out why on the copy.
More on Security & maintenance
An administrator account on the site and, where the work needs it, the hosting control panel — each of us with an account of our own rather than a shared login, because a shared password is one nobody can revoke. Every account is removed the day the work ends, and you can remove them yourself at any point without asking us.
More on Security & maintenance
A redesign, new features, new pages built from scratch, and anything that is really a development project wearing a maintenance hat. We will say so rather than let it drift into the routine, and quote it separately. Third-party licences and the hosting itself are yours either way.
More on Security & maintenance
No, and anybody who says yes is selling a checklist. The whole method here is that the measurement comes first: the reason a site is slow is different every time, and it is almost never the thing people guess before looking.
More on Speed & performance
We will not answer that before measuring, and the studios that do are quoting somebody else's site. What we can tell you after the audit is what each fix is worth in the numbers we measured, so you can decide which ones are worth doing.
More on Speed & performance
No. Most of the work is in the site rather than under it, and we do this on hosting we do not sell and cannot see the inside of. If the server really is the limit we will show you the measurement that says so, and it is still your decision.
More on Speed & performance
No. A score is a summary of measurements, and it can be improved without making anything faster — the section above this one lists the usual ways. The goal is the page feeling quicker to the people who use it, which is what the field data measures and what a laboratory run only approximates.
More on Speed & performance
The work happens on a copy first, a restore point is taken before the live site is touched, and every change goes on one at a time so a regression has one suspect. Performance work that removes a feature is not performance work, and we will not do it without telling you which feature and asking.
More on Speed & performance
Usually not on its own. What is usually the problem is a page builder rendering through forty plugins, a theme loading everything on every page, and images uploaded at camera resolution. All three are fixable without leaving WordPress, and we will say so if leaving it really is the cheaper answer.
More on Speed & performance
Speed is one input among many and nobody outside the search engines knows the weights, so anyone promising you positions is guessing. What is true and checkable is that Core Web Vitals are collected from real visits to your site and are used, and that the technical work here — crawlability, rendering, redirect chains, duplicate URLs — is the part of SEO that is engineering rather than opinion.
More on Speed & performance
Until somebody adds a plugin, a tag or a hero video. That is not cynicism, it is how sites work — which is why the audit tells you what to watch, and why continuous monitoring belongs with maintenance rather than being sold as part of a one-off speed job.
More on Speed & performance
Often not, and we would rather say so before you have paid for one. If nothing about it needs the camera, location, notifications or working offline, and people would open it now and then rather than daily, a web application does the same job with no install, no review queue and no store rules to keep up with.
More on Mobile apps
It depends on whether the device is the point. If the product is forms, lists, accounts and content, cross-platform with Flutter or React Native is usually right, and pretending otherwise is how a budget doubles. If it leans on the camera, sensors, background work or real offline use, native Swift and Kotlin are worth what they cost. We will tell you which in writing, with the reasoning.
More on Mobile apps
You do, from the first commit. The repository is yours, the Apple and Google developer accounts are registered to your company, the servers are in your name, and we work inside them as team members rather than holding them. There is no version of this where leaving is expensive.
More on Mobile apps
That is our problem, not yours, and it is part of the work rather than the point where the work stops. The rules that catch people are account deletion, sign-in options, privacy disclosures, payments inside the app and anything that looks like a website in a wrapper — all decided while building rather than argued about after a rejection.
More on Mobile apps
Yes, and from the second stage onwards. Test builds go to your own phone through TestFlight on iPhone and internal testing on Android, so you are tapping the real thing long before anybody else can see it.
More on Mobile apps
Almost always, as soon as there are accounts, anything shared between users, notifications or data that has to survive a lost phone. We build it as part of the app rather than as a second project, or connect properly to a system you have — and it can run on your cloud account or on our own servers.
More on Mobile apps
We will not name a number before knowing what it has to do, and the studios that do are quoting an app that is not yours. What we commit to is a shape and a figure in writing after the first stage, and a test build on your phone before the expensive part begins.
More on Mobile apps
More than people expect and less than they fear. Apple and Google change requirements every year, libraries age, and an app nobody has touched for two years usually cannot be released at all without work first. Planning for that from the start is cheaper than discovering it, which is why it is a stage in the process above rather than an upsell after it.
More on Mobile apps
Usually, and it is a large part of what we do. The first thing is an honest read of what is there — what builds, what is tested, which libraries are abandoned, which store deadlines are coming — and a written answer on whether continuing or rebuilding is cheaper.
More on Mobile apps
Buy, if a product does it and your process can bend to fit — it is cheaper, and somebody else keeps it running. Build when the way you work is the advantage, when several tools are retyping the same data, or when the software is what you sell. We will tell you which in writing, even when the answer is a subscription.
More on Software development
You do, from the first commit. The repository, the database and the servers are in your name, and we work inside them rather than holding them. Your data is exportable in formats that are not ours. There is no version of this arrangement where leaving is expensive.
More on Software development
Carefully, and more than once. The migration is written as a repeatable step rather than a one-off copy, run against your real data early, and the old system kept running beside the new one until the figures agree. The switch happens when there is nothing left to be surprised by.
More on Software development
Wherever suits you: your own cloud account, or our own servers, which is the other half of what this company does. Nothing in it is written to depend on where it lives, so moving it later is a configuration change rather than a project.
More on Software development
Usually — accounting, e-commerce, CRM, payment providers and anything else with an API. Integrations are built to survive the other end being down: retried safely, never applied twice, and logged so a person can see what happened.
More on Software development
Roles and permissions are part of the first design rather than a later feature. Secrets stay out of the code, every account has only the access it needs, changes that matter are recorded, and dependencies are kept current as part of the work rather than when something breaks.
More on Software development
We will not name a number before knowing what it has to do, and the studios that do are quoting a project that is not yours. What we commit to is a shape and a figure in writing after the first stage, and something your team can click before the expensive part begins.
More on Software development
Yes, and it is designed in from the first release: accounts and roles, subscriptions and invoices through a payment provider, each customer's data kept apart, and the administration side you will need on the day the first customer asks for something unusual.
More on Software development
Usually, and it is a large part of what we do. The first thing is an honest read of what is there — what runs, what is tested, what is abandoned — and a written answer on whether continuing, modernising in pieces or rebuilding is cheaper. We will show you the reasoning either way.
More on Software development
No, and they are often confused. A certificate encrypts the connection between a browser and your server, so nobody can read what passes between them. It does nothing about what is stored at the end of that connection. This scans the files and the application themselves. You want both, and they are not substitutes.
More on Website protection
Five things: a malware scan of your files, an FTP scan, a scan of the web application itself, a SQL injection scan and a cross-site scripting scan. All five are in every plan — none of them is an upgrade. What the plan changes is the frequency: weekly, daily, or continuously. The table on this page says which is which.
More on Website protection
No. Nothing moves. Setting it up is FTP details in the panel and one check that you own the site — that triggers the first scan. Your host, your control panel and your files stay exactly where they are.
More on Website protection
It is removed rather than added to a report for you to act on — but how often it may do that is a real difference between the plans. The entry plan removes malware once, during the initial scan. The middle one does it up to twice a month. Only the top plan is unlimited. If you are buying this because something keeps coming back, that is the line to read.
More on Website protection
A snippet you put in your footer once the site has been scanned and is clean. It tells somebody about to type a card number that the site is being checked. We will give you the snippet, and place it for you if you would rather not touch the template.
More on Website protection
On one-year terms. That is how the product is sold, so it is what we quote — there is no monthly version and we are not going to imply there is.
More on Website protection
No. There is none on this product, and you are reading that here rather than finding it in a clause afterwards. If you are not sure it is right for you, say so in the form and we will tell you honestly whether it is.
More on Website protection
On the top plan only, along with OWASP top-ten blocking and dynamic caching. The table on this page marks exactly which plan carries them, rather than leaving you to find out after buying.
More on Website protection
Not directly. It opens from the management page in your account rather than from its own URL, which is worth knowing before you go looking for a login page that does not exist.
More on Website protection
No, and anybody who says otherwise is selling. A daily scan tells you what got through; updating is what stops it getting through. If updates are the actual problem, our security and maintenance page is the honest answer.
More on Website protection
No. Scanning changes the odds; a backup is what saves you on the day something goes wrong anyway — including the days that have nothing to do with security, which is most of them.
More on Website protection
Web Hosting is a product with fixed tiers. Business Hosting is an assembled platform: the resources, retention policy and support arrangement are agreed with you rather than picked from a table.
More on Business Hosting
Because the shape is decided in conversation. Publishing a figure for work that has not been specified would be a guess dressed up as a quote.
More on Business Hosting
That is the usual starting point. The migration is planned around your release calendar, with the current environment serving traffic until you decide to switch.
More on Business Hosting
Yes. Access is scoped per environment, so a client can reach their own site without seeing the rest of your portfolio.
More on Agency Solutions
The environment transfers to their own account. Nothing is rebuilt and DNS does not change, so the site does not notice.
More on Agency Solutions
The arrangement is worth having once you are managing enough sites that access and billing have become the work. We will say so honestly if you are not there yet.
More on Agency Solutions
Current PHP and Node releases with pinned minor versions, plus static builds. Anything else is worth a conversation rather than a promise on a marketing page.
More on Developer Infrastructure
The API is the contract. Anything that can be created in the console can be created from a script, which is what makes a declarative wrapper possible.
More on Developer Infrastructure
Yes. Deployment can be triggered by your existing pipeline rather than replacing it, if your build already lives somewhere you are happy with.
More on Developer Infrastructure
Any Mac running macOS 13 Ventura or later. The application is a universal binary, so it runs natively on Apple Silicon and on Intel — there is one download and it is the right one.
More on DigiCode
No. That is the point of it. The web server is PHP's own, using the PHP already on your machine, and MySQL installs into the application's own folder. Nothing is placed on the system and nothing has to be running before you start.
More on DigiCode
Because it is signed but not notarised by Apple, which is a paid certificate rather than a security finding. Open it the first time with a right click and then Open, and every launch after that is normal. Installing through Homebrew skips the step entirely.
More on DigiCode
Swift, JavaScript, Python, PHP, HTML, CSS and JSON, through Tree-sitter — a real parse of the grammar rather than a set of regular expressions. The language is recognised from the file extension and shown in the status bar.
More on DigiCode
Yes. DigiCode drives the git installed on your machine rather than reimplementing it, so your configuration, credentials, signing keys and hooks all apply unchanged.
More on DigiCode
Yes. Recipes are YAML or JSON files in the application's recipes folder, and one carrying the same id as a built-in recipe replaces it. A step runs an executable and its arguments rather than a shell line, and every path is resolved inside the project folder.
More on DigiCode
Everything lives in one folder inside your Library — MySQL and its data, your recipes, and what was running for each project. Deleting that folder returns the application to a fresh state without touching your projects.
More on DigiCode
One Homebrew command, or drag the application to the Trash. A second command removes its data as well — the database, the recipes and the preferences.
More on DigiCode
Still stuck
Tell us what you are trying to do rather than what went wrong, and we will tell you whether it is something we can fix from here.
There is no ticket robot in front of us. What you write is what somebody reads.
The fastest answers come from the message that explains the goal, not only the error.
Sign in first and we can see the account the question is about without asking you to describe it.