Technologies
The tools we build with, and why.
Each technology comes with a plain account of when ATPL chooses it and when it does not. No stack is right for every job, and saying so is part of the engineering.
Stack path
Technologies we use
- 01
Job
What must run
- 02
Pick
Fit, not fashion
- 03
Wire
Into the system
- 04
Keep
Years later
- 16
- Years building technology
- Derived from the start year
- 100+
- Websites shipped
- October 2019 milestone
- 15+
- Mobile applications
- ATPL company facts
01
Eight technologies
And when we choose them
Hover or focus a row to see when ATPL reaches for it. Each page also lists when it does not.
Back end
Front end
Content management
02
How we approach this
Approach
This website runs on Next.js. For client work the stack is chosen per project, after the problem is understood, and each page here says when its technology is the wrong pick.
01
Scoped to one job first, so the first release is small and real.
02
Source code in a repository you control from day one.
03
The same engineers support what they built after launch.
03
Questions people ask
FAQ
The questions asked before buying, answered plainly. If yours is not here, ask it on the contact page.
ATPL builds with Laravel and PHP, React, Next.js, Node.js, Vue.js and Python, and works with WordPress for sites a client’s own team must edit. The choice follows the job: for example, Next.js for sites that must rank in search, Python for data and AI work.
Choose Laravel when the application is forms, records and reports over a relational database and a small team will maintain it. Choose Node.js when the work is real-time, event-driven or mostly APIs. ATPL builds with both and will recommend one once it understands the job.
ATPL takes on existing codebases in the technologies listed here. The first step is a review of the code and the hosting, so that any quote is based on what is actually there rather than on a rewrite by default.