Softwarity builds software for the people who build software inside companies. Our ground is the internal applications an IT department carries: the ones with real users, real data, real access rules, and a small team behind them.
Those teams all end up writing the same things. A login page. A role model. A user table. An audit trail somebody asked for after an incident. A gateway configuration nobody dares touch on a Friday. That work is necessary, it is never the point, and it is where the weeks go.
Our answer is to take that half out of the application and put it where it belongs: in front of it. That is what Meerkat is, and it is the shape of everything we make - the repetitive part becomes a product, so the part that is yours stays yours.
Meerkat, the authentication proxy and API gateway: one door in front of an internal application, which takes charge of authentication, access rules, organisations, routing, quotas and audit. Its ancestor, Archway, did the same job on a Spring Cloud Gateway stack. It taught us what to do differently - and how much further the idea could be taken.
plug puts a developer's workstation inside a cluster, so a service running on a laptop answers under its cluster name and everything else goes on as before.
A shelf of Angular components we needed, published rather than copied from project to project: navigation rails, row actions, loading indicators, timezone pickers. See Open source.
Putting a gateway in front of your applications is a long commitment, so here is what it buys you on our side.
You can check the product before you trust it. What is built and what is not is one table in the repository, read from the code rather than from a plan. Nothing on this site says "coming soon" about something that does not exist.
You are not locked in. The core is source-available and becomes plain Apache 2.0 two years after each release, so what you deploy today cannot be taken away from you. Your whole configuration exports as one file you can read and replay elsewhere. And the gateway sends us nothing, ever - there is no telemetry in it.
When something goes wrong, you reach the people who wrote it. There is no support tier between you and the code.