Why I built beanquery: a whitelist-first query API for JPA
Generic filter endpoints over JPA entities are convenient and dangerous. beanquery flips the default: nothing is queryable until you say so.
I’m Mirek, a software developer from Poland with 20 years of professional Java experience: from banking systems at Asseco, through leading a development team, to running my own company, REXOFT. Today I work as a senior Java developer on integrations, publish what I learn as open source (beanguard, beanquery, beanboot) and work with AI every day, while keeping the architecture, and the responsibility for it, in my own hands.

Licensing system for Java/Spring Boot apps: issue, encrypt and verify licences with a self-hosted server, admin panel and customer shop.
Whitelist-first REST query API over JPA entities: annotate your entities, get /metadata and /query endpoints with safe filtering.
Spring Boot auto-configuration for users and groups, JWT auth, audit logs and distributed scheduling.
Generic filter endpoints over JPA entities are convenient and dangerous. beanquery flips the default: nothing is queryable until you say so.
How beanguard issues, encrypts and verifies licences for Java applications, and how you enforce limits and features with annotations.
What I hand to AI, what I keep, where it goes wrong, and the two files that keep Claude on course.