Code that's built to maintain.
This page answers the technical questions a CTO or senior engineer asks before signing. What we use by default, how we ship, and what we avoid.
The tools we reach for first.
These are our defaults — chosen to move fast with confidence. We adapt to your context: existing stack, compliance constraints, team preferences.
Frontend & UI
Next.js 16 · React 19 · TypeScript · Tailwind v4 · Framer Motion · React Hook Form · Zod
Backend & API
Node.js / TypeScript · Python / FastAPI · Postgres · Supabase or self-hosted · REST + tRPC
Data & ML
Postgres (OLTP) · DuckDB / Snowflake / BigQuery (big data) · Polars · dbt · Airflow / Dagster · PyTorch · pgvector / Qdrant (RAG)
Infrastructure & DevOps
Vercel · AWS / GCP / Azure · Cloudflare · Terraform · GitHub Actions · Docker · Kubernetes (when justified)
Observability
Datadog · Sentry · Grafana · structured logs · distributed tracing · SLO dashboards
How we ship.
Tests at multiple levels
Unit (Vitest, pytest), integration on critical flows, Playwright e2e when it's worth the cost. Coverage scales with criticality — not an arbitrary number.
Strict types everywhere
TypeScript strict mode, Pydantic or dataclasses in Python. Types catch 80% of bugs before runtime — we lean into that systematically.
Systematic reviews
Every change goes through review (human + AI-augmented). Trade-offs are documented in the PR or an ADR — never only in the developer's head.
Automated CI/CD
GitHub Actions or GitLab CI. Lint, type-check, tests, build, deploy. No manual production deploys.
Useful documentation
Up-to-date README, ADRs for structural decisions, runbooks for routine operations. No dead wikis, no lying docs.
Observability from day 1
Structured logs, traces, alert dashboards. When something breaks in production, we know before your customer does.
The code belongs to you.
No lock-in. You can take over alone or hand off to another vendor any time — that's the guarantee we document for, as if we were leaving tomorrow.
- Repo in your GitHub or GitLab organization from day 1.
- No hidden vendor dependency — code is readable by another dev without any Acynx context.
- All keys, secrets, infra access under your control (shared vault, never only in our heads).
- Documentation written for the next maintainer, not for us.
- No proprietary platform lock-in — your data stays exportable.
The non-negotiable basics.
Law 25 (Quebec)
Privacy impact assessments for any personal data processing. Privacy policy kept up to date with every delivery.
Secrets management
1Password, AWS Secrets Manager or Hashicorp Vault depending on context. No secrets in a repo in plaintext — ever.
Mutual NDA
We can sign your standard NDA or use ours, compliant with Quebec law. Our collaborators are bound by the same commitments.
Audit trails
Access logs, full git history, traces of infrastructure operations. Everything is traceable — nothing is silent.
What we don't use.
A few tools and practices we avoid when building software that needs to last. Strong preferences — discussed case by case if the context truly justifies it.
No-code for critical products
Bubble, Webflow, Retool can prototype fast, but become a wall when the product needs to scale or integrate deeply. We build in code as soon as we know it has to live.
Abandoned or end-of-life frameworks
We pick technologies with active communities and visible roadmaps. Inheriting an obsolete stack costs more than migrating now.
Tech debt accepted out of laziness
Shortcuts are allowed — when they're documented as such, with a repayment date. Otherwise no.
Ready to ship?
A 20-minute call is enough to identify the right plan and the first request to launch.