Well he does briefly mention the three best-known frameworks for server-side Swift (Vapor, Kitura, and Perfect) in the middle of the piece, when he talks about

Well he does briefly mention the three best-known frameworks for server-side Swift (Vapor, Kitura, and Perfect) in the middle of the piece, when he talks about middleware. But I think the thrust of this piece is eschewing currently-available frameworks and rethinking what we have come to think a "web framework" should do, and doing those things with a interchangeable plain-vanilla Swift approach, a sort of "Swift-is-my-framework" approach. (I might be missing something, though, because I've only skimmed the post and added it to my read-later list...)