Frequently asked questions

A focused piece of work, such as a booking system or a rebuilt site, usually lands in the low five figures. A platform your business runs on is larger. We will not pretend to know your number before we understand the problem, but you will have a fixed written figure before you commit to anything, and the conversation that gets us there is free.

Most projects run six to sixteen weeks from go-ahead to live. You see working software throughout, so you are never waiting months to find out whether we understood you.

Expected, and fine. We price the change, you approve it in writing, then we build it. Nothing gets added to your invoice that you have not agreed to first.

You do, completely, from the day it is delivered. Source code, accounts, domains and documentation, all registered to your business. We keep no rights over it and no ability to switch it off.

You keep everything and we help the next team pick it up. This is the question worth asking every developer you speak to, because the usual answer involves a hosting account only they can access.

Often, yes. We will review what exists and give you a straight read on whether it is worth continuing or whether you are better off rebuilding. Sometimes the answer costs us the bigger job, and we will still give it to you plainly.

Yes, across Australia and overseas. Most of the work happens remotely either way, and we are happy to meet in person if you are local.

An independent AI research and development lab in Brisbane, Queensland, Australia. We build and operate our own products, publish research and open-source tools, and take on client software work in web platforms, AI systems, security and computer vision.

Small. Human engineering amplified by a fleet of AI agents doing the work that scales that way. We say so plainly rather than implying a larger team than exists.

Brisbane, Queensland, Australia. We work with clients across Australia and overseas.

DominionOS and WeftScript are public on GitHub. The HumanOR detection engine is open source. Others are commercial, and each product page says which it is.

Email [email protected], or use the form on the contact page. We reply within one business day.

Email [email protected], or follow the machine-readable policy at /.well-known/security.txt. We run a bounty board and we pay for findings.

First-party analytics only: page views, referrer, campaign parameters, coarse device class and performance timings, with no cookies used for advertising and no personal information in event payloads. The full detail is in the privacy policy and the cookie policy.

No. Directive 02: your data is yours. We do not sell it, mine it, or anonymise it into a product.

Email [email protected] from the address the data relates to. The process and the timelines are set out on the data requests page.

We handle personal information in line with the Australian Privacy Principles regardless of turnover thresholds, because the alternative is deciding which of your customers deserve the protections.

Yes. Search and AI-search crawlers — Googlebot, Bingbot, Applebot, GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Amazonbot and others — are allowed on the public content. The policy is in robots.txt and explained on the crawler policy page.

Yes: /llms.txt is an LLM-oriented index of the site with the canonical entity description and links to every important page. /sitemap.xml, /rss.xml, /atom.xml and /openapi.json are also served.

No. Every public page is server-rendered static HTML that is complete without JavaScript, and it is byte-identical regardless of user agent.

Only abusive ones. Vulnerability scanners, credential stuffing, enumeration and request floods are blocked. Legitimate crawlers, monitoring services and accessibility tooling are allowed.