product
Web applications
Typed from the database to the button. Server-rendered, fast on first load, and built so the second feature is as easy to add as the first.
Software engineering: design, build, operate
Systems built to survive contact with production.
NickTeck is a software development and engineering company. We take products from the first schema to the running server: web, desktop and mobile applications, the APIs behind them, the AI features inside them, and the infrastructure that keeps them online.
- TypeScript
- Rust
- PostgreSQL
- Docker
- Self-hosted or cloud
What we build
Eleven kinds of work, one team doing all of it.
Most projects need more than one of these. The same engineers cover the whole path, so the schema, the interface and the server agree with each other.
desktop
Desktop applications
The same product as a real desktop app for Windows, macOS and Linux, packaged as an installer with updates that land on their own.
mobile
Mobile and installable apps
Phone and tablet builds, plus progressive web apps that install straight from the browser and keep working offline.
commerce
Online stores and checkout
Headless storefronts where the catalogue, cart and checkout are built as a real application rather than bolted onto a template.
platform
APIs and services
HTTP and realtime interfaces, background workers, and scheduled jobs. Documented, versioned, and safe to call twice.
data
Data and storage
PostgreSQL schemas with migrations you can run forward under load, plus the search, caching and object storage around them.
realtime
Realtime and collaboration
Multi-user editing, presence, and live updates, with conflict resolution handled rather than hand-waved.
ai
AI features and integration
AI-powered features in the product you already have: assistants over your own data and agents that call your APIs, with guardrails, cost limits and a human in the loop where it counts.
infra
Infrastructure and deployment
Containerised builds, TLS, backups, monitoring and rollback, set up before launch day rather than after the first incident.
managed-it
Managed IT and support
The systems your business runs on rather than the ones it sells: networks and Wi-Fi, Microsoft 365 and identity, backups you have actually restored from, cameras and access control, and the servers still sitting in the building.
migration
Migrations and rescue work
Moving off a legacy system, or picking up a codebase someone else left behind. We map what exists before we change it.
Not on the list
If your problem is not here, ask anyway.
This is where most of our work lands, not a menu. Some things are still in research rather than on offer, and plenty of projects do not fit a heading at all. Describe the problem and we will tell you honestly whether we are the right people for it.
AI integration
AI, integrated like the rest of the system.
AI-powered features in the product you already have, built the way any other dependency would be: retrieval, permissions, cost limits and guardrails around the model. And we will tell you when a query or a rule would serve you better than one.
- Fits the product you have
- Provider integration, streaming interfaces and cost caps, added to a live application without destabilising it.
- Answers come from your data
- Assistants that read your own content at question time and cite the source they answered from.
- Bounded by design
- Typed tool contracts, spend limits per request, and a human approving anything that cannot be undone.
- Measured every release
- Evals scored on each change, with cost, latency and failure rates watched in production.
We also build with AI tooling ourselves. Every line of it is read and owned by an engineer before it reaches your repository. How that works.
Working stack
What we reach for by default.
Not a wish list. This is what we run in production. We will use something else when a project genuinely calls for it.
- Languages
- TypeScriptRustSQLJava / KotlinBashOthers as needed
- Runtime
- BunNode.jsJVMLinux
- Interface
- ReactTailwind CSSVite
- Desktop and mobile
- TauriElectronProgressive web appsOffline sync
- Data
- PostgreSQLMongoDBRedisS3-compatible storage
- Realtime
- WebSocketsSocket.IO
- AI
- Claude and OpenAI APIspgvectorMCPEvals
- Operations
- DockerNginxGitHub ActionsOpenTelemetry
- Verification
- VitestPlaywright
How an engagement runs
Four stages, in this order, every time.
You always know which stage the work is in and what comes out of it.
01
Scope
We start with constraints rather than features: what has to be true, what already exists, and what breaks if it goes down. You get a written plan, a technical approach, and a way to start: a fixed price for the first milestone, or a set number of hours a week run in four-week cycles.
- Technical plan
- Milestone breakdown
- Fixed quote or weekly hours
02
Build
Short cycles against a running environment. The work is deployed somewhere you can open from the first week, so review happens continuously instead of arriving as a surprise at the end.
- Preview environment
- Weekly demo
- Open issue tracker
03
Ship
Launch is a checklist, not an event: migrations rehearsed, backups verified, monitoring wired up, rollback tested. We put the system into production and watch it settle.
- Release checklist
- Monitoring and alerts
- Rollback plan
04
Operate
We stay on for as long as you need us: a support retainer, ongoing feature work, or a clean handover with documentation your own team can act on.
- Support agreement
- Operating instructions
- Handover documentation
Tell us what needs building.
Send a few sentences about the problem. You will get a written reply from an engineer within one business day, not a sales sequence.