Show HN: Authorizer – open-source auth for enterprise apps and agents https://ift.tt/n5wyMiO

Show HN: Authorizer – open-source auth for enterprise apps and agents I'm Lakhan, the creator and maintainer of Authorizer. I've been working on it for a few years. Authorizer is an open-source authentication and authorization server that can be self-hosted. The project started around authentication for applications and users. Over time, I started running into a broader set of problems involving services, workloads, and agents making requests. That's a big part of what led to the work in 2.4. One area I spent a lot of time on was delegation. An agent can need to act on behalf of a user and then call another service or agent. Passing the user's original access token through every step makes it difficult to keep the user's permissions separate from the permissions of the agents acting on their behalf. Authorizer 2.4 adds OAuth token exchange using RFC 8693 for this. Delegated tokens carry an actor chain, and the effective scope is attenuated based on the subject token, the agent's allowed scopes, and the requested scope. The release also adds service accounts using OAuth client credentials for machine-to-machine authentication. Service accounts can authenticate using JWT bearer assertions, SPIFFE JWT-SVID, or Kubernetes TokenReview when workload identity is configured. Another significant part of the release is MCP. Authorizer can expose its MCP surface over Streamable HTTP and protect it as an OAuth 2.1 resource server. It implements protected resource metadata, Dynamic Client Registration, Client ID Metadata Documents, and RFC 8707 audience binding for the MCP endpoint. The release also adds a number of enterprise identity features: SAML 2.0 and OIDC federation, SCIM 2.0 user and group provisioning, organizations, WebAuthn/passkeys, and relationship-based authorization using an embedded OpenFGA engine. Service accounts can also be represented as first-class subjects in the authorization model, so authorization can distinguish between a user and an autonomous workload. I wanted Authorizer to remain self-hostable. There are good hosted authentication services, but some teams need to run their identity infrastructure themselves or want control over where it runs. If you want to try Authorizer, there is a Railway deployment template: https://ift.tt/8TrQJd0... The source is here: https://ift.tt/9mHJs38 Getting started: https://ift.tt/txXuGsm The complete 2.4.0 changelog: https://ift.tt/ycptRUk... I'm particularly interested in how other teams are handling identity and delegation when agents need to call multiple services or act on behalf of users. https://ift.tt/9mHJs38 September 2, 2026 at 03:50AM

Show HN: Windrunner – AI-powered project collaboration workspace https://ift.tt/NHzKleR

Show HN: Windrunner – AI-powered project collaboration workspace https://shzlw.github.io/windrunner/ September 2, 2026 at 02:19AM

Show HN: Campsend – open-source Alternative to WeTransfer https://ift.tt/9Lh6SbI

Show HN: Campsend – open-source Alternative to WeTransfer Campsend is the open-source alternative to WeTransfer for creatives. It allows you to see when clients have opened and downloaded files, revoke access to links, create branding for your links, bring your own storage and use it within your LLM as well. https://campsend.app/ September 1, 2026 at 10:09PM

Show HN: MQLens – A Native MongoDB GUI (SSH, X.509, Kerberos, No Electron) https://ift.tt/ymY0xLQ

Show HN: MQLens – A Native MongoDB GUI (SSH, X.509, Kerberos, No Electron) https://mqlens.com/ September 1, 2026 at 03:08AM

Show HN: Keeplea – photograph everything you want to remember https://ift.tt/dzbBXGV

Show HN: Keeplea – photograph everything you want to remember At some point I noticed how many photos I take just to remember something, to come back to it later, when I need it. The packaging of a product I liked, a notice on the door of some government place, small paper documents, screenshots of something that felt important at the time. Well, even the wiring inside the walls during a renovation, photographed "for the future". All of it lands in the photo gallery next to the "real" photos, and then you almost never come back to any of it, because finding one specific thing in that random stream is just not realistic. Yes, modern mobile OSes categorize photos automatically and let you search the text on them. But the categorization is primitive, like "mountains", "documents", "screenshots", and the thing you're looking for isn't always written on the photo. The native photo gallery will never find me that photo of the wiring behind the kitchen wall. There's no text on it, and "wiring" is not a category. So the idea was a mobile app where all these utility photos go, and I don't have to maintain them in any way - automatic categorization, with semantic search on top. Give it a try and let me know what you think: Website: https://keeplea.app Get the app: https://get.keeplea.app So far it's all pretty hard. No users yet - an app like this has low "search" potential, nobody types this problem into a store search box. But I'll keep trying, as they say. Under the hood: KMP, native UI, Firebase, Gemini, Firestore vector search. P.S. Let me say it right away: this app wasn't vibecoded over the weekend, as people like to put it these days. Honestly, I hate the term "vibecoding". It downplays the weeks and months that go into thinking through the idea, the architecture, the experiments, the design, the marketing, etc. The fact that you use AI agents while building doesn't mean you slapped something together and spat it into production. Although, true, plenty of people nowadays do exactly that. Well, not me https://keeplea.app/ September 1, 2026 at 02:40AM

Show HN: I built a live stream site where every spot is instantly AI-generated https://ift.tt/dUKWjbY

Show HN: I built a live stream site where every spot is instantly AI-generated https://videoai.me/live September 1, 2026 at 12:35AM

Show HN: Unitpost/email – open-source Email Components and Layouts https://ift.tt/xFIcCT3

Show HN: Unitpost/email – open-source Email Components and Layouts If you are using React, you've probably used or heard of React Email by Resend. Ironically once we started building Unitpost we hit the limit: React Email works when an engineer owns a .tsx file. Add a designer or an agent and you get a second copy that drifts. So we built @unitpost/email. One inbox-safe document for Outlook, Apple Mail, and Gmail. React or string TSX. 24+ transactional and marketing emails 20+ pre-built email layouts 15+ components npx skills add unitpostcom/email and the AI you already use can generate the emails. https://ift.tt/k7Ub0fv August 31, 2026 at 11:30PM