A Drupal practice that shows its work.
Building with Drupal since 2007, from Drupal 6 to Drupal 11. Today Drupal Developer is the Drupal practice of White Wolf Technology LLC, doing business as D-E-V.com.
Who does the work
The practice is led by Jacob Baloul, who has built and run software for about thirty years and has worked with Drupal since 2007, starting with Drupal 6: high-availability and security work, e-commerce, travel and food platforms, and the LAMP stack that Drupal grew up on.
Day to day, the engineering is done by a supervised team of AI agents, each with a defined role: Drupal developer, systems administrator, security reviewer, QA tester. Work is checked by a different agent from the one that did it, and nothing reaches your production site without a human sign-off. You can read how that team works, including the mistakes, at godofbots.org.
An American company, an American team
Drupal Developer is part of White Wolf Technology LLC, an American-owned company. The practice is American-led and the people who answer for your site are Americans. Our AI agents are tools that this team runs and supervises; they never replace a human sign-off.
Credentials and experience
Certified
- Drupal Certified Developer
- Drupal Certified Site Builder
- AWS Certified Solutions Architect Professional and DevOps Engineer Professional
- AWS Certified Solutions Architect, Developer and SysOps Associate
- Two US patents in artificial intelligence
Experience includes
Drupal architecture, performance and security work for Time Inc. (TIME, Sports Illustrated, People), NBC Sports during the Olympics, Fidelity, Prudential, Citi, IBM, Johnson & Johnson, Raytheon, College Board, National Geographic, MDVIP, eBay / StubHub and the New York State Office of the State Comptroller.
Drupal built for billions of page views, for live events of more than 100 million page views an hour, and for more than one million product pages on a single build.
How we work
Look before touching
Every engagement starts read-only. We measure the site as it is before we propose a change.
Git is the truth
What runs in production is what is in the repository. If they differ, fixing that comes first.
Rehearse, then release
Changes are tried on a copy rebuilt from your backup, and every release has a rollback we have tested.
Evidence, not adjectives
We do not call a site “secure” without the output that shows it. You get that output.





