<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>NexifyPro Blog</title>
    <link>https://nexifypro.com/blog</link>
    <description>Articles from the NexifyPro team on product development, DevOps, data and AI, security and quality engineering.</description>
    <language>en</language>
    <atom:link href="https://nexifypro.com/blog/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Five signs you bought a vulnerability scan, not a penetration test</title>
      <link>https://nexifypro.com/blog/vulnerability-scan-vs-penetration-test</link>
      <guid isPermaLink="true">https://nexifypro.com/blog/vulnerability-scan-vs-penetration-test</guid>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
      <description>A penetration test is defined by its scope and method, not its tool. How to tell the difference from the report in your hands, how to buy the real thing, and how to run the automated half continuously.</description>
      <dc:creator>Praveen Kumar</dc:creator>
      <category>Security</category>
      <category>Penetration testing</category>
      <category>AppSec</category>
    </item>
    <item>
      <title>Tenant isolation belongs in the database, not the dashboard</title>
      <link>https://nexifypro.com/blog/tenant-isolation-belongs-in-the-database</link>
      <guid isPermaLink="true">https://nexifypro.com/blog/tenant-isolation-belongs-in-the-database</guid>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
      <description>Shared-schema multi-tenancy with row-level security, the tenant carried per transaction, BI filters as defence in depth, and a test that tries to read tenant B as tenant A on every route.</description>
      <dc:creator>NexifyPro Engineering</dc:creator>
      <category>Architecture</category>
      <category>Multi-tenancy</category>
      <category>PostgreSQL</category>
      <category>Data</category>
    </item>
    <item>
      <title>Stop stuffing the prompt: an agent platform where domain teams own the tools</title>
      <link>https://nexifypro.com/blog/stop-stuffing-the-prompt</link>
      <guid isPermaLink="true">https://nexifypro.com/blog/stop-stuffing-the-prompt</guid>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
      <description>Most assistants die at the second feature. The shape that survives: the model pulls what it needs through tools designed for it, built by the teams who own the data, reviewed against one contract.</description>
      <dc:creator>Praveen Kumar</dc:creator>
      <category>AI</category>
      <category>Agents</category>
      <category>MCP</category>
      <category>Architecture</category>
    </item>
    <item>
      <title>SOC 2 and HIPAA controls you can prove with Terraform, not screenshots</title>
      <link>https://nexifypro.com/blog/soc2-hipaa-controls-with-terraform</link>
      <guid isPermaLink="true">https://nexifypro.com/blog/soc2-hipaa-controls-with-terraform</guid>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
      <description>A large share of SOC 2 and HIPAA technical controls are infrastructure configuration. Implement them once in Terraform, check them continuously, export the evidence by script, and buy a compliance platform only for the people workflows.</description>
      <dc:creator>Praveen Kumar</dc:creator>
      <category>Compliance</category>
      <category>AWS</category>
      <category>Terraform</category>
      <category>Security</category>
    </item>
    <item>
      <title>ECS Fargate or EKS: the same container deployed both ways, with the bill</title>
      <link>https://nexifypro.com/blog/ecs-fargate-or-eks-with-the-bill</link>
      <guid isPermaLink="true">https://nexifypro.com/blog/ecs-fargate-or-eks-with-the-bill</guid>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
      <description>The eight questions that decide the platform before any benchmark, two Terraform stacks for the same service, the bill at 2, 10 and 50 services from published prices, and where EKS earns its keep.</description>
      <dc:creator>Praveen Kumar</dc:creator>
      <category>Cloud</category>
      <category>AWS</category>
      <category>Containers</category>
      <category>Kubernetes</category>
    </item>
    <item>
      <title>Build-Operate-Transfer fails in the Transfer. Here are the gates to negotiate at signing.</title>
      <link>https://nexifypro.com/blog/build-operate-transfer-fails-in-the-transfer</link>
      <guid isPermaLink="true">https://nexifypro.com/blog/build-operate-transfer-fails-in-the-transfer</guid>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
      <description>BOT engagements rarely fail while a vendor is building. They fail when nobody defined what 'stable' means, who owns the accounts, or why the vendor would ever let go. The scorecard, the ownership matrix and the terms that fix it.</description>
      <dc:creator>Praveen Kumar</dc:creator>
      <category>Delivery</category>
      <category>Build-Operate-Transfer</category>
      <category>Engineering leadership</category>
    </item>
    <item>
      <title>AI coding assistants make some teams slower. Here is how we keep them fast.</title>
      <link>https://nexifypro.com/blog/ai-coding-assistants-slower-teams</link>
      <guid isPermaLink="true">https://nexifypro.com/blog/ai-coding-assistants-slower-teams</guid>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
      <description>The evidence says assistants amplify whatever discipline a team already has. The practices, the measurements and the operating agreement we use so they amplify the right things.</description>
      <dc:creator>Praveen Kumar</dc:creator>
      <category>AI</category>
      <category>Engineering practice</category>
      <category>Delivery</category>
    </item>
    <item>
      <title>Welcome to the NexifyPro blog</title>
      <link>https://nexifypro.com/blog/welcome-to-the-nexifypro-blog</link>
      <guid isPermaLink="true">https://nexifypro.com/blog/welcome-to-the-nexifypro-blog</guid>
      <pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate>
      <description>What we will write about here, and why a services company should share what it learns while building for clients.</description>
      <dc:creator>Praveen Kumar</dc:creator>
      <category>Company</category>
    </item>
    <item>
      <title>Hosting a Next.js site as static files on S3 and CloudFront</title>
      <link>https://nexifypro.com/blog/static-nextjs-on-s3-and-cloudfront</link>
      <guid isPermaLink="true">https://nexifypro.com/blog/static-nextjs-on-s3-and-cloudfront</guid>
      <pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate>
      <description>How this website is built and deployed: a static Next.js export, a private S3 bucket behind CloudFront, and a GitHub Actions pipeline that publishes on every push.</description>
      <dc:creator>NexifyPro Engineering</dc:creator>
      <category>AWS</category>
      <category>Next.js</category>
      <category>DevOps</category>
    </item>
  </channel>
</rss>
