Company
An engineering studio built on shipping.
JPCLOW designs and builds production software for companies and institutions — with the rigor of an engineering team and the focus of a small studio.
01JPCLOW
Where we come from
JPCLOW was founded by João Paulo Santos after years of working inside the operations it now builds software for: ERP support, industrial planning and maintenance, commodity logistics, and university innovation programs.
That background shapes how we work. We start from the operation — the people, the data, and the constraints — and only then choose the technology. The result is software that fits the business instead of forcing the business to fit the software.
02How we work
How we work
Production early
Working software on a real URL from the first sprint. Feedback beats speculation.
Decisions in writing
Every relevant trade-off is recorded, so your team understands why the system looks the way it does.
Boring where it matters
Proven tools for the core, innovation only where it creates a real advantage.
Quality is a feature
Performance, accessibility, and observability are part of the scope, not extras.
Operational background
2025 — Present
Universidade de Rio Verde - UniRV
Software Developer (Scholar)
2025 — 2026
Louis Dreyfus Company
Planning & Control Intern
2024 — 2024
Aliare
ERP Support Assistant
2022 — 2024
Klabin
Planning & Maintenance Assistant
03Sectors
Domains we already know.
Context shortens projects. These are the domains we have built for — live platforms, research, and prototypes, each with its status stated on the case study.
Innovation & education
Portals and ecosystems for universities, incubators, and public innovation programs.
Related work
Operations & services
Software for individual riders and field work, plus a customer self-service prototype for service companies.
Related work
Digital products & AI
Consumer products with privacy, offline capability, and AI at the core.
Related work
04Under the hood
Engineering standards, not afterthoughts.
The quality bar that ships with every project — the same one this website is built on.
// edge/api/orders.ts — typed, validated, observableimport { z } from 'zod';import { withTracing, problem } from '@/lib/platform'; const Order = z.object({ customerId: z.string().uuid(), items: z.array(LineItem).min(1),}); export default withTracing(async (request, env) => { const body = Order.safeParse(await request.json()); if (!body.success) return problem(422, body.error); const order = await env.DB.orders.create(body.data); await env.QUEUE.send({ type: 'order.created', id: order.id }); return Response.json(order, { status: 201 });});Type-safe end to end
Strict TypeScript and validated boundaries between client, API, and database.
Performance budgets
Static and edge-first delivery with Core Web Vitals tracked in production.
Accessible by default
WCAG 2.1 AA as the target: keyboard paths, contrast, and reduced-motion support.
Observable in production
Error tracking, structured logs, and real-user metrics from the first deploy.
Tested pipelines
Unit and end-to-end tests run in CI before anything reaches production.
Secure by design
Least privilege, bot protection, and encryption where user trust depends on it.
Reference architecture
L1Interface
- Astro
- SvelteKit
- React
- HTMX
- Tailwind
L2Application
- Django
- Workers
- REST / BFF
- Queues
L3Data
- Postgres
- Neon
- Supabase
- IndexedDB
L4Infrastructure
- Cloudflare
- Docker Swarm
- CI/CD
- Sentry
Next step
Have a system to build or a process to fix?
Tell us about the problem. You get a first technical read, a suggested path, and next steps.