How We Deliver

How we actually work

This page answers "how exactly do you do it?" It's not marketing copy: it's our actual technology choices, our delivery standards, and which steps need your confirmation.

Technology Choices

We decide based on what you need, not to use a particular brand. Right now we mainly use:

Back end: Python with FastAPI and SQLAlchemy
Database: PostgreSQL (production), SQLite for development
Front end: HTML and CSS built on the server before being sent. Only pages that need a lot of interaction get a front-end framework, after a separate review
Deployment: Docker containers, with a reverse proxy handling certificates and domains
Version control: Git

We choose tools that are mature, well documented, maintainable over the long term, and easy for someone else to take over at any time. We don't stack multiple frameworks or use obscure technology that locks clients in.

Quality Checks Before Delivery

Everything we produce is checked item by item before delivery. We never hand clients anything that hasn't been checked:

Each feature is tested and the results are recorded
Content involving facts, figures, regulations, and quotations is checked against its sources item by item
Your data is used only for this service and is never given to third parties
Steps that need your confirmation (payments, deleting data, publishing, sending messages, changing the live system) always get your written confirmation first
These steps are listed one by one on the quote

If your industry or contracts have special disclosure requirements about how work is done, please note it on the request form and we'll provide a written explanation as you require.

What we do on every project

Each feature is tested and the results are recorded
Check dependencies for known vulnerabilities
Permission checks happen on the server, not by hiding things in the browser
Passwords are stored only as hashes
Keys and passwords are kept in environment variables, never in version control or sent to the browser
Error messages don't reveal internal details
Backups and restores are actually tested
Deployment documents and rollback steps

This Website

The site you're looking at now was built the way described above: rendered on the server, with no third-party tracking and no external JavaScript. To see how far that goes in practice, take a look at Data Security.