Matched to your stack, not to ours.

We do not arrive with a preferred framework and propose a rewrite. If your platform is a .NET monolith that works, the right assignment is usually an engineer who knows .NET rather than a migration nobody asked for. Where a stack genuinely is the constraint, we will say so and give the reason.

A technology missing from this list is a sourcing question rather than a no. The list covers what recurs across current engagements — it is not a boundary, and it is not the order in which we would recommend adding capacity. That starts from the bottleneck, which is what our service lines are organised around.