--- title: "About us" description: "Twenty years of PHP, one long-term partner for legacy platform migration - not a generalist agency, and not outside the framework you're migrating onto." og: image: images/app/opengraph/og-aboutus.png --- # About us Twenty years of PHP, one long-term partner - not a generalist agency that also does migrations. We help established businesses move off aging PHP platforms without stopping the business to do it. Every engagement runs on the same principle as the migrations themselves: incremental, not a leap of faith. We start with what you're actually running, not a template, and build the plan from there - it fits your system, not the other way around. ## Our Approach Every migration starts with an audit, not a quote. We identify the risks, the hidden costs, and the parts of your system nobody wants to touch, then put a number on all three. That's what lets us deliver in phases instead of promising a rewrite that only pays off two years from now. The goal is not just a working handoff, but a codebase your own team can extend after we're gone. ## Our Team Most of our engineers are ZCE (Zend Certified Engineers), and Apidemia is an official Laminas commercial vendor, one of a short list endorsed by the technology's own stewards. Two decades in the PHP ecosystem means we've built on, and migrated away from, nearly every generation of it. We know what breaks in a migration because we've been the team called in to fix it when someone else's didn't work. ## Two Projects, One Goal Dotkernel isn't a fork of Laminas or Mezzio, and it isn't a wrapper you'll outgrow either - it's built directly on top of them. Mezzio is the PSR-15 middleware runtime of the Laminas Project, which is "The Linux Foundation's only PHP project" and the open-source continuation of [Zend Framework](https://getlaminas.org/about/). So when we migrate you onto Dotkernel, you're landing on components with real, active stewardship behind them - not something only we maintain. ![Laminas Project, Dotkernel Headless Platform](/images/pages/two-projects-one-goal.svg) ## Founder and CTO When we say we know this framework, we don't mean we've read the docs. Julian Somesan (arhimede), our founder and CTO, sits on the Technical Steering Committee for both the [Laminas Project](https://github.com/laminas/technical-steering-committee/blob/master/MEMBERS.md) and Dotkernel - the group that decides where these frameworks go next - and is a contributor for [php[architect]](https://www.phparch.com/community/julian-somesan/). He's also the one who wrote [the blog post](https://getlaminas.org/blog/2024-07-02-dotkernel-a-replacement-for-laminas-api-tools.html) announcing the TSC's own recommendation - after placing Laminas API Tools in security-only mode in January 2023 - to move to Dotkernel API instead. ## Contribution This isn't a team that only consumes Laminas and Mezzio - we help maintain them. Two of our engineers are public, verified members of both the Laminas and Mezzio GitHub organizations, and several others have contributed updates over the years too. Where that work landed matters more than how much of it there was - pull requests from our team shipped updates to the actual components your Dotkernel application would run on: - `laminas/laminas-session` - `mezzio/mezzio-session` - `mezzio/mezzio-session-ext` - `mezzio/mezzio` - `laminas/laminas-config-aggregator` - `laminas/laminas-json-server` The rest of our contributions sit in project infrastructure - `laminas/getlaminas.org`, the TSC repository - not framework code, and we're not going to pretend otherwise. That's the difference between a vendor who uses your framework and one who helps build it. ## The Bottom Line If your migration runs into a real limitation in Laminas or Mezzio, you're not stuck waiting on someone else's roadmap. That's what comes from working with a team that sits inside the project, not outside it.