<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Permissions on Pi Stack</title><link>https://www.pistack.xyz/tags/permissions/</link><description>Recent content in Permissions on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 18 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/permissions/index.xml" rel="self" type="application/rss+xml"/><item><title>SpiceDB vs OpenFGA vs Permify: Self-Hosted Authorization Engines 2026</title><link>https://www.pistack.xyz/posts/spicedb-vs-openfga-vs-permify-self-hosted-fine-grained-authorization-guide-2026/</link><pubDate>Sat, 18 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/spicedb-vs-openfga-vs-permify-self-hosted-fine-grained-authorization-guide-2026/</guid><description>&lt;p>When you move beyond simple role-based access control (RBAC), permissions get complicated fast. &amp;ldquo;Can user X view document Y, but only if they&amp;rsquo;re in the same organization, haven&amp;rsquo;t been blocked by user Z, and the document hasn&amp;rsquo;t expired?&amp;rdquo; Hard-coding that logic into your application is a recipe for bugs, security holes, and endless refactoring.&lt;/p></description></item></channel></rss>