01The work
Pure Artisan
A multi-vendor marketplace for regional producers across Belgium and the Netherlands. We own the whole platform — architecture, frontend, backend, integrations, deployment. Still in build.
The brief
Give small producers somewhere to sell that is not a supermarket listing or an Instagram DM. Two countries, four languages, real payments and real shipping from the first release.
How we built it
A NestJS API over PostgreSQL, a server-rendered Next.js storefront, Meilisearch for search and Mollie for payments. The vendor dashboard is the part we spent longest on: a cheesemaker has to be able to list a product without reading a manual. Shipping matches on postal code, because Belgian delivery zones do not respect provincial borders.
- Languages
- NL · FR · EN · DE
- Markets
- Belgium, Netherlands
The rest of what we have built is under NDA, so it is not on this page. We can talk through comparable work on a call.
What it is made of
4 layers
Storefront
Next.js, React, Tailwind. Server-rendered, four locales.
API
NestJS. Vendors, orders, payouts, shipping rules, invoicing, VAT.
Data
PostgreSQL for the record, Redis for the queues, Meilisearch for the catalogue.
Infrastructure
Cloudflare R2 and CDN, CI/CD, Mollie Connect for vendor payouts.
02What we do
Five things, properly.
We would rather be genuinely good at a short list than available for everything. If your project needs something outside it, we will say so rather than learn on your budget.
Next.js on the front, NestJS and PostgreSQL behind it, TypeScript the whole way through. Multi-tenant and multi-language where the project genuinely needs it, real-time where it earns its keep, and a deployment pipeline you could hand to another team without an apology.
Usually
- Next.js
- NestJS
- TypeScript
- PostgreSQL
- Redis
LLM features against OpenAI, Claude or Mistral. Semantic and faceted search. Content and translation pipelines — we run automated translation across four languages against a catalogue that keeps changing under it. Most of the interesting work is deciding what the model is not allowed to do, and what happens when it is confidently wrong.
Usually
- OpenAI
- Claude
- Mistral
- Meilisearch
React Native and Expo where one codebase genuinely serves both stores, native where the app needs something one does not give you. Built against the same API as the web platform, so the two cannot drift apart. App Store and Play Store submission, review rejections and the release cycle are part of the job — that is usually the part people underestimate.
Usually
- React Native
- Expo
- Swift
- Kotlin
Odoo implementation, custom modules, and integration with whatever else is already in the building — CRM, stock, accounting, HR. Data migration is part of the job rather than a line item, because migration is where these projects actually go wrong.
Usually
- Odoo
- Python
- JSON-RPC
- PostgreSQL
Code review and vulnerability assessment, 2FA and MFA, encrypted data paths, rate limiting and DDoS mitigation, and guidance where PCI-DSS applies. On anything we build, this is included rather than quoted separately.
Usually
- OWASP
- 2FA / MFA
- Cloudflare
- PCI-DSS
Not sure which of these your project is? Describe it and we will tell you.
03The studio
You hire the people who build it.
J-TECH started as things we built for ourselves. People saw them and asked whether we would do the same for them, and that turned out to be a business.
We work out of Wavre and take clients wherever they are — a timezone is a scheduling problem, not a filter. The client list stays short on purpose: fewer projects, more attention on each, and no account manager relaying your brief to a team you never meet.
We are not the cheapest quote you will get and we are not trying to be. We are selective about what we take on, partly because we are small, and partly because the work is better when the problem is genuinely interesting to us.
How it goes
- 01
You send a brief
The form below, or an email. As much or as little detail as you actually have.
- 02
We read it and reply
It comes from whoever would build it. That reply is a proposal, a question, or an honest "not us" — we send all three.
- 03
We agree and start
Scope, timeline and cost settled before anything begins. Then you talk to the person doing the work, for the length of the project.
04Start
Tell us what you are building.
Or write to us directly
Where we are
Clos des Eclaireurs1301 Wavre
Belgium
We answer everything, including the projects we turn down.