Disclaimer

Everything published on this site by MI Technologies is general information. It is written carefully and in good faith, but it cannot account for your specific circumstances.

Reading an article here is not the same as receiving advice about your situation. If a decision matters commercially, discuss it with someone who knows the details of your case — whether that is us or anyone else.

Our technical articles reflect our experience and our reading of the tools at the time of writing. Two honest caveats apply.

First, technology moves. A recommendation that was correct when published may be outdated later. We update material where we can, but assume anything more than a year old may have aged.

Second, reasonable engineers disagree. Where we take a position — on architecture, on a framework, on when to build versus buy — it is a considered opinion, not settled fact. We have tried to explain our reasoning so you can judge whether it applies to you.

Code examples and configuration shown on this site are illustrative. Test anything before running it in production.

Where this site mentions cost ranges or delivery timelines — including in articles about what software costs — those figures are illustrative and based on typical projects.

They are not quotations, and they do not constitute an offer. Your project may cost significantly more or less depending on scope, integrations, data complexity and how quickly decisions are made.

A figure applicable to you can only come from a scoping conversation, and it will be given in writing with its assumptions stated.

Software can improve a business. It cannot guarantee one.

Nothing on this site should be read as a promise about revenue, growth, conversion rates, search rankings, funding outcomes or operational savings. Those depend on your market, your team, your execution and factors none of us control.

Where we describe a benefit — faster pages, fewer errors, less manual work — we are describing what the engineering aims to produce, not warranting a commercial outcome.

Statements about performance, scalability or reliability describe what well-built software can achieve under reasonable conditions. Actual results depend on infrastructure, data volume, traffic patterns and third-party services.

Any specific figure we publish in a case study will be a real measurement from a real project, taken with the client’s agreement, with the measurement conditions stated. We do not publish rounded-up numbers or industry averages presented as our own.

This site links to external documentation, tools and services where they are genuinely useful. We do not control those resources and are not responsible for their content, availability or practices.

A link is not an endorsement of the organisation as a whole, and naming a technology does not imply any partnership, certification or affiliation with its vendor unless we say so explicitly.

We try to keep this site accurate and available, and we correct errors when we find them or when they are pointed out. We do not warrant that content is complete, current or error-free, or that the site will be uninterrupted.

If you spot something wrong, tell us. We would rather fix it than leave it.

To the extent permitted by law, we accept no liability for loss arising from reliance on general information published here.

This does not affect our obligations under a signed engagement contract, which are governed by that contract, nor does it limit liability that cannot lawfully be limited.