Forjed
What we do

Products we own, and work we take on.

We take on a small number of client engagements at a time, held to the same standard as our own products — documented, tested, and handed over in a state your team can maintain without us.

Consultancy

Architecture reviews, technical due diligence, and upgrade paths that don’t turn into rewrites. Useful when the decision is expensive to reverse.

What this covers

  • Architecture and code reviews
  • Technical due diligence for acquisitions and investment
  • Upgrade and migration planning
  • Second opinions on expensive decisions

Development

Embedded with your team, or owning the build end to end. Laravel and PHP, Rust, Vue on the front, native where it earns its place.

What this covers

  • Embedded engineers inside your team
  • End-to-end product builds
  • Laravel, PHP, Rust and Vue; native (SwiftUI) where it earns its place
  • Regulated environments, including banking

Platform & tooling

Local environments, deployment, release and the developer experience in between. Yerd came out of solving exactly this for ourselves.

What this covers

  • Local development environments
  • Deployment and release pipelines
  • Developer experience and internal tooling
How it works

How an engagement works.

  1. 01

    A conversation

    Tell us what you’re building and what it has to survive. No commitment, just a chat about whether we can help.

  2. 02

    Agree how to work

    If it’s a fit, we work out together what makes sense: an estimate for a defined piece of work, or an hourly or daily rate for something ongoing.

  3. 03

    Build

    Documented and tested as we go, in your repositories.

  4. 04

    Handover

    In a state your team can maintain without us, with maintenance available if you want it.

Common questions

Before you get in touch.

If your question isn’t here, email us directly — a person answers, and it will usually be one of the founders.

hello@forjed.io

It starts with a conversation, not a contract. We talk about what you’re building and whether we can help; if it makes sense to work together, we agree how — an estimate for a defined piece of work, or an hourly or daily rate for something ongoing. If we don’t think we’re the right studio for the work, we’ll say so and point you at someone who is.

Most of our work starts in one. We begin by reading it properly — tests, deployment, the parts nobody wants to touch — and favour incremental changes over a rewrite unless a rewrite is genuinely the cheaper path.

It depends on the work, so we don’t publish a rate card. Once we’ve talked it through, we can give you an estimate or agree an hourly or daily rate — whichever suits the work.

Yes, and it’s often the best arrangement. We work in your repositories, follow your review process, and leave documentation and tests behind so your team owns the result.

Yes. We offer ongoing maintenance — framework and dependency upgrades, security patches and small improvements — so what we build keeps working long after launch.

Got something that has to keep working?

Tell us what you’re building and what it has to survive. We’ll start with a conversation, not a proposal — and an honest answer about whether we’re the right studio for it.