<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:webfeeds="http://webfeeds.org/rss/1.0">
    <channel>
        <title><![CDATA[Xano Developer Hub]]></title>
        <description><![CDATA[Xano Developer Hub]]></description>
        <link>https://community.xano.com</link>
        <generator>Bettermode RSS Generator</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:10:44 GMT</lastBuildDate>
        <atom:link href="https://community.xano.com/rss/feed" rel="self" type="application/rss+xml"/>
        <pubDate>Wed, 18 Nov 2026 19:10:44 GMT</pubDate>
        <copyright><![CDATA[2026 Xano Developer Hub]]></copyright>
        <language><![CDATA[en-US]]></language>
        <ttl>60</ttl>
        <webfeeds:icon></webfeeds:icon>
        <webfeeds:related layout="card" target="browser"/>
        <item>
            <title><![CDATA[Add labels to allowed IPs in the Connector]]></title>
            <description><![CDATA[Today, when we add allowed IP addresses in the Connector, the list only shows the raw IPs. Once the list grows, we can't tell what each one is: which server, office, machine or service it belongs to.

...]]></description>
            <link>https://community.xano.com/product-feedback-xjjbnyli/post/add-labels-to-allowed-ips-in-the-connector-BRUe2JI36akTKBE</link>
            <guid isPermaLink="true">https://community.xano.com/product-feedback-xjjbnyli/post/add-labels-to-allowed-ips-in-the-connector-BRUe2JI36akTKBE</guid>
            <category><![CDATA[ip-whitelist]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[xano connector]]></category>
            <dc:creator><![CDATA[MeuCombate]]></dc:creator>
            <pubDate>Sun, 15 Nov 2026 14:57:47 GMT</pubDate>
            <content:encoded><![CDATA[<p>Today, when we add allowed IP addresses in the Connector, the list only shows the raw IPs. Once the list grows, we can't tell what each one is: which server, office, machine or service it belongs to.</p><p><strong>Request:</strong> add an optional label (name or tag) field to each IP entry, for example:</p><ul><li><p><code>203.0.113.10</code> – Production server (AWS)</p></li><li><p><code>198.51.100.24</code> – Office network</p></li><li><p><code>192.0.2.55</code> – John's laptop (dev)</p></li></ul><p><strong>Why it matters:</strong></p><ul><li><p><strong>Clarity:</strong> we'd know right away where each IP comes from.</p></li><li><p><strong>Safer cleanup:</strong> we could remove old or unused IPs without worrying about breaking something that still depends on them.</p></li><li><p><strong>Auditing:</strong> reviewing who has access would be quicker, especially in teams.</p></li></ul><p>It would also help to be able to edit the label later and to search or filter the list by label.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cannot push changes from AI assistant when it's affect a table]]></title>
            <description><![CDATA[Hi. I have an issue who happen multiples times with the ai assistant, when the changes require to modify one of my tables it's simply impossible to push changes even after waiting X hours, how fix ...]]></description>
            <link>https://community.xano.com/discussion-and-questions-1kv6mqqm/post/cannot-push-changes-from-ai-assistant-when-it-s-affect-a-table-ymiqEHSDt1OO8XB</link>
            <guid isPermaLink="true">https://community.xano.com/discussion-and-questions-1kv6mqqm/post/cannot-push-changes-from-ai-assistant-when-it-s-affect-a-table-ymiqEHSDt1OO8XB</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[assistant]]></category>
            <category><![CDATA[breaking changes]]></category>
            <category><![CDATA[tables]]></category>
            <dc:creator><![CDATA[Girz.ai]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 07:40:20 GMT</pubDate>
            <content:encoded><![CDATA[<p>Hi. I have an issue who happen multiples times with the ai assistant, when the changes require to modify one of my tables it's simply impossible to push changes even after waiting X hours, how fix this issue ? Thanks</p><figure data-type="image" data-version="v2" data-id="C54qAE4l8RbmbootUAGru" data-size="best-fit" data-align="center"><img src="https://tribe-s3-production.imgix.net/C54qAE4l8RbmbootUAGru?auto=compress,format" data-id="C54qAE4l8RbmbootUAGru"></figure>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is Xano working on something like Row Level Security? (asking for a friend who vibe coded past me)]]></title>
            <description><![CDATA[Hi all,

Yesterday a former client proudly showed us what they had vibe coded all by themselves. I’ll be honest: I was impressed. And slightly worried about my job security. 😄

They picked Supabase as ...]]></description>
            <link>https://community.xano.com/discussion-and-questions-1kv6mqqm/post/is-xano-working-on-something-like-row-level-security-asking-for-a-GsThFWWo9Cg76eN</link>
            <guid isPermaLink="true">https://community.xano.com/discussion-and-questions-1kv6mqqm/post/is-xano-working-on-something-like-row-level-security-asking-for-a-GsThFWWo9Cg76eN</guid>
            <category><![CDATA[Product & Design]]></category>
            <category><![CDATA[Record Security]]></category>
            <dc:creator><![CDATA[Bas van Ginkel]]></dc:creator>
            <pubDate>Wed, 04 Nov 2026 15:31:04 GMT</pubDate>
            <content:encoded><![CDATA[<p>Hi all,</p><p>Yesterday a former client proudly showed us what they had vibe coded all by themselves. I’ll be honest: I was impressed. And slightly worried about my job security. 😄</p><p>They picked Supabase as their backend, and one of the main reasons was <strong>Row Level Security</strong>. Looking at what they built, I get it. With their limited backend knowledge, RLS acted like a safety net: once the rules are set, everything they build afterwards automatically sticks to them. They could move fast <em>and</em> stay reasonably secure, which is usually a “pick one” situation.</p><p>That got me wondering: <strong>is Xano working on something like this?</strong></p><p>Right now, every endpoint is its own little security checkpoint. You have to remember to filter on <code>$auth.id</code>, check ownership, verify roles... every single time. It works, and with discipline (and code reviews) it’s fine, but it only takes one forgotten filter on one endpoint for data to end up where it shouldn’t.</p><p>Imagine defining access rules once at the table level, using <code>$auth.id</code> as the starting point. Something like “users can only read records where <code>user_id = $auth.id</code>” or “members can access records belonging to their organisation”. Every query would respect those rules by default, unless you explicitly bypass them.</p><p>For me that would be a game changer in both development speed and peace of mind. It would also make Xano a lot friendlier for less experienced builders and AI-assisted development, where you really want the platform to protect you from yourself.</p><p>So I’m curious:</p><ul><li><p>Is something like this on the roadmap?</p></li><li><p>How do you handle this today? Reusable functions, middleware, strict naming conventions, prayer?</p></li><li><p>Would you even want RLS-style rules in Xano, or do you prefer the explicit per-endpoint control?</p></li></ul><p>Would love to hear how other developers look at this!</p><p>Cheers,<br>Bas</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Core Workspace / Centralized Logic]]></title>
            <description><![CDATA[Does anyone know where to find the functionality described in the below video? The video states that docs are in the description. I can't find any documentation or information on the features ...]]></description>
            <link>https://community.xano.com/discussion-and-questions-1kv6mqqm/post/core-workspace-centralized-logic-xFvzlu9wabfbI2O</link>
            <guid isPermaLink="true">https://community.xano.com/discussion-and-questions-1kv6mqqm/post/core-workspace-centralized-logic-xFvzlu9wabfbI2O</guid>
            <category><![CDATA[Centralized Logic]]></category>
            <category><![CDATA[Core Workspace]]></category>
            <dc:creator><![CDATA[Dahrl Payne]]></dc:creator>
            <pubDate>Wed, 28 Oct 2026 22:19:27 GMT</pubDate>
            <content:encoded><![CDATA[<p>Does anyone know where to find the functionality described in the below video? The video states that docs are in the description. I can't find any documentation or information on the features discussed. <br><br>In short, I believe the functionality described consists of placing logic/functions that can be used across different workspaces into a single centralized "core" workspace. Therefore sharing  those functions to all workspaces, while only needing to make updates or changes to any of those functions from a single location.<br><a href="https://www.xano.com/use-case/logic-centralization/" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered">https://www.xano.com/use-case/logic-centralization/</a></p><div data-type="embed" data-id="OHOEQ4WCCS43bbByd42dT" data-embed-url="https://www.xano.com/use-case/logic-centralization/"></div><p><br><a href="https://www.youtube.com/watch?v=jG2PCtfSaaQ" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered">https://www.youtube.com/watch?v=jG2PCtfSaaQ</a></p><div data-type="embed" data-id="1HGqxLQe6R1OM7w3qeTIa" data-embed-url="https://www.youtube.com/watch?v=jG2PCtfSaaQ"></div>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Xano 2.7: Tenant Deployment Approvals, Expanded MCP Capabilities, and Security Updates]]></title>
            <description><![CDATA[Release 2.7 introduces new deployment approval workflows and expanded MCP capabilities, giving teams greater control over production releases and more ways to integrate AI into their applications.

Here...]]></description>
            <link>https://community.xano.com/release-announcements-mv6qq2wj/post/xano-2-7-release-j9o3NiZJ0mfiWxa</link>
            <guid isPermaLink="true">https://community.xano.com/release-announcements-mv6qq2wj/post/xano-2-7-release-j9o3NiZJ0mfiWxa</guid>
            <dc:creator><![CDATA[Holly Brennan]]></dc:creator>
            <pubDate>Wed, 28 Oct 2026 20:48:51 GMT</pubDate>
            <content:encoded><![CDATA[<p>Release 2.7 introduces new deployment approval workflows and expanded MCP capabilities, giving teams greater control over production releases and more ways to integrate AI into their applications.</p><p>Here's what's new.</p><h2 id="e0440afd-6877-4007-9d88-c22fe18ec868" data-toc-id="e0440afd-6877-4007-9d88-c22fe18ec868" class="text-xl"><strong>Tenant Deployment Approvals</strong></h2><p>Teams can now require approval before deploying a release to a specific environment, such as production. This adds oversight to the deployment process, helping organizations enforce separation of duties, strengthen security controls, and support audit and compliance requirements.</p><p>With Tenant Deployment Approvals, you can:</p><ul><li><p><strong>Require deployment reviews:</strong> Configure approval requirements for individual tenants, such as production environments, without changing the deployment process for others.</p></li><li><p><strong>See exactly what's changing:</strong> Compare a proposed release against what's currently deployed, including file-by-file differences.</p></li><li><p><strong>Enforce separation of duties:</strong> By default, the person requesting a deployment cannot approve their own request, helping teams maintain independent review. Permissions can be configured to allow exceptions.</p></li><li><p><strong>Collaborate on reviews:</strong> Add comments, request changes, and track decisions.</p></li><li><p><strong>Maintain consistent controls:</strong> Approval workflows are supported in the UI, Metadata API, CLI, and Developer MCP tools, with activity captured in audit logs.</p></li></ul><p>Approval requirements are optional and use Xano's existing role-based permissions.</p><p>For teams with stricter security and compliance requirements, deployment approvals provide a way to introduce formal review and maintain an auditable record of changes before they reach production.</p><p><em>Tenant Deployment Approvals requires a Xano Custom plan. Contact our team to learn more.</em></p><h2 id="ad7b6367-4392-48ce-bc70-49fa25018130" data-toc-id="ad7b6367-4392-48ce-bc70-49fa25018130" class="text-xl"><strong>Expanded MCP Capabilities</strong></h2><p>We've upgraded MCP servers to support a newer MCP specification, introducing several new capabilities for developers building AI-powered applications and integrations.</p><p><strong>Prompts and resources</strong></p><p>MCP servers can now expose reusable prompts and resources alongside tools. Both are built using Xano function stacks and support the same development workflows as other workspace objects, including branching, Git sync, and releases.</p><p><strong>OAuth authentication</strong></p><p>Secure access to your MCP servers with OAuth authentication. Choose Xano-hosted authentication or connect your existing identity provider. This enables users to securely connect your MCP servers to Claude and other AI clients that require OAuth, making it easier to bring your application's tools and data into AI-powered workflows.</p><p><strong>More capable tools</strong></p><p>MCP tools can now return structured outputs, report progress during execution, and request additional input from users when needed. You can also add titles, icons, and behavioral hints to help clients understand how tools work.</p><p><strong>Live updates</strong></p><p>Connected clients can receive notifications when available tools, prompts, or resources change.</p><p><strong>Backward compatibility</strong></p><p>Existing MCP clients and tools continue working without changes. Xano automatically handles requests from clients using older and newer versions of the specification.</p><h2 id="c412ea79-c4a6-49c3-b586-e0e4fd47eabb" data-toc-id="c412ea79-c4a6-49c3-b586-e0e4fd47eabb" class="text-xl">PHP Runtime Security</h2><p>Release 2.7 includes a permanent fix for two PHP runtime vulnerabilities (CVE-2026-109618 and CVE-2026-109619), building on the security patch already applied to all instances.</p><h2 id="9e8f2475-11bf-4803-b5dc-38f07451a702" data-toc-id="9e8f2475-11bf-4803-b5dc-38f07451a702" class="text-xl"><strong>Available in Release 2.7</strong></h2><p>These updates make it easier to manage production deployments and build more sophisticated MCP integrations directly within Xano.</p><p>Explore these new capabilities in your workspace today. For more details, check out the <a href="https://docs.xano.com/updates" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered">full release notes</a>.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Xano builders: what AI task would you try with free API credits?]]></title>
            <description><![CDATA[Hey everyone — are you adding an AI feature to a Xano app? What’s the part you’d most like to test before spending more on API calls?

I’m vita from the Tokatlas team. We’re a commercial multi-model API...]]></description>
            <link>https://community.xano.com/discussion-and-questions-1kv6mqqm/post/xano-builders-what-ai-task-would-you-try-with-free-api-credits-pBVdGS6s0DWRs03</link>
            <guid isPermaLink="true">https://community.xano.com/discussion-and-questions-1kv6mqqm/post/xano-builders-what-ai-task-would-you-try-with-free-api-credits-pBVdGS6s0DWRs03</guid>
            <dc:creator><![CDATA[Ziwei Yao]]></dc:creator>
            <pubDate>Wed, 28 Oct 2026 06:20:23 GMT</pubDate>
            <content:encoded><![CDATA[<p>Hey everyone — are you adding an AI feature to a Xano app? What’s the part you’d most like to test before spending more on API calls?</p><p>I’m vita from the Tokatlas team. We’re a commercial multi-model API platform, and we’re running a 20-spot free API-credit trial for developers with real projects. The 20 spots are shared across our community outreach, not 20 per site.</p><p>For Xano builders, I’d love to hear about one specific backend task: extracting fields from a document, generating a draft, or an agent making several model calls. Tell us what goes in, what a useful result looks like, and which model or API features you need. A short description is plenty.</p><p>We’ll select a mix of suitable use cases and confirm the model, endpoint, credit scope and expiry before you start. This is an invitation to test your workflow, rather than a prebuilt Xano template. Please keep API keys, customer data and private code out of the comments.</p><p>To join, reply here or email <a href="mailto:affiliates@tokatlas.com" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered">affiliates@tokatlas.com</a> with “Xano trial” and a few lines about your project. Replies close November 2, 2026, at 15:59 UTC; we’ll share selected usernames and next steps here within three days. No purchase, upvote or positive review required.</p><p>Take a look: <a href="https://app.tokatlas.com" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered">https://app.tokatlas.com</a></p><p>What would you put through its paces first?</p><p>One concrete backend scenario: an AI extraction request times out, and the webhook sender retries. Before writing to your database, decide how you will identify the same business event, validate required fields, and route incomplete results to review. A useful acceptance case is sending the same synthetic event twice and checking whether it creates one business record.</p><p>Where would you put that duplicate check in your Xano workflow: before the model call, before the database write, or both?</p><p>If you would like to discuss a trial workflow privately, message us on WhatsApp: <a href="https://wa.me/13032576528?text=Hi%2C%20I%27d%20like%20to%20try%20Tokatlas%2E" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered">https://wa.me/13032576528?text=Hi%2C%20I%27d%20like%20to%20try%20Tokatlas%2E</a></p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Missing data on user's table]]></title>
            <description><![CDATA[Hi there,

is there anyone having issues on user's table, in this case, missing the email and sometimes other info? i mean, the email field is going to null with no reason

I've contacted support, but no ...]]></description>
            <link>https://community.xano.com/discussion-and-questions-1kv6mqqm/post/missing-data-on-user-s-table-4WBkTrKaDXHbN5N</link>
            <guid isPermaLink="true">https://community.xano.com/discussion-and-questions-1kv6mqqm/post/missing-data-on-user-s-table-4WBkTrKaDXHbN5N</guid>
            <category><![CDATA[error]]></category>
            <dc:creator><![CDATA[André Ferreira]]></dc:creator>
            <pubDate>Fri, 23 Oct 2026 09:25:25 GMT</pubDate>
            <content:encoded><![CDATA[<p>Hi there,</p><p>is there anyone having issues on user's table, in this case, missing the email and sometimes other info? i mean, the email field is going to null with no reason</p><p>I've contacted support, but no feedback yet. This is impactating my application, and i wonder if someone has the same problem</p><p>Thanks</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Separate record information from table definitions]]></title>
            <description><![CDATA[Hi there - I'm just getting into AI development and set my environment up with git to track changes and collaborate with the team before pushing using the CLI.

A couple of times already I have nearly ...]]></description>
            <link>https://community.xano.com/product-feedback-xjjbnyli/post/separate-record-information-from-table-definitions-tkLrZRESRzDDy6I</link>
            <guid isPermaLink="true">https://community.xano.com/product-feedback-xjjbnyli/post/separate-record-information-from-table-definitions-tkLrZRESRzDDy6I</guid>
            <dc:creator><![CDATA[Ryan Heath]]></dc:creator>
            <pubDate>Wed, 21 Oct 2026 10:25:57 GMT</pubDate>
            <content:encoded><![CDATA[<p>Hi there - I'm just getting into AI development and set my environment up with git to track changes and collaborate with the team before pushing using the CLI. </p><p>A couple of times already I have nearly committed a table definition that includes pulled records in the items[] array. </p><p>Is there a recommended approach for avoiding this? Or can we have data in separate files so it can be included in gitignore?</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Support Branch-specific and DataSource-specific connections in Realtime V2]]></title>
            <description><![CDATA[Realtime V2 introduces support for managing Realtime servers, channels, messages, and triggers. However, websocket clients can only connect to the live branch, which creates a significant limitation ...]]></description>
            <link>https://community.xano.com/product-feedback-xjjbnyli/post/support-branch-specific-and-datasource-specific-connections-in-realtime-v2-mjBuBf9wukChR9j</link>
            <guid isPermaLink="true">https://community.xano.com/product-feedback-xjjbnyli/post/support-branch-specific-and-datasource-specific-connections-in-realtime-v2-mjBuBf9wukChR9j</guid>
            <category><![CDATA[Engineering]]></category>
            <category><![CDATA[Product & Design]]></category>
            <dc:creator><![CDATA[Francisco Azevedo]]></dc:creator>
            <pubDate>Fri, 16 Oct 2026 11:00:08 GMT</pubDate>
            <content:encoded><![CDATA[<p>Realtime V2 introduces support for managing Realtime servers, channels, messages, and triggers. However, websocket clients can only connect to the live branch, which creates a significant limitation when developing and testing Realtime functionality without affecting production.</p><p>Although creating a separate Realtime server has been suggested as a workaround, this does not fully solve the problem, since the server still executes against the live branch. Its underlying functions and handlers must therefore also exist in production, breaking branch isolation and forcing developers to maintain duplicated servers, functions, and handlers just to test changes safely.</p><p>Ideally, Realtime V2 should allow clients to connect directly to a specific branch, following the same principle already available for API requests. For example, if an API request can target a specific branch (eg: "branch2") using <code>https://host/api:can:branch2/endpoint</code>, a similar mechanism could be supported for websocket connections, such as <code>wss://host/ws/can:branch2</code>.</p><p>In addition to specifying the branch, it should also be possible to specify the Data Source for the connection using an <code>x-data-source</code> parameter, allowing developers to select both the branch and the Data Source independently. For example: <code>wss://host/ws/can:branch2?x-data-source=test</code>.</p><p>This would provide full control over the execution environment, allowing developers to test Realtime functionality against the appropriate branch and Data Source without affecting production data or logic.</p><p>This capability would make Realtime V2 more consistent with the existing Xano development workflow, eliminate the need for production-based workarounds, and significantly improve the safety and efficiency of Realtime development.</p><p>FA</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[State of Xano Q3 2026: Building AI Software for Production]]></title>
            <description><![CDATA[Hello Xano Developers!

At the end of Q2, we talked about how quickly AI is changing software development. Three months later, that shift is only accelerating.

It has never been easier to build software....]]></description>
            <link>https://community.xano.com/release-announcements-mv6qq2wj/post/state-of-xano-q3-2026-HlIqxzOqS5Uvlx4</link>
            <guid isPermaLink="true">https://community.xano.com/release-announcements-mv6qq2wj/post/state-of-xano-q3-2026-HlIqxzOqS5Uvlx4</guid>
            <dc:creator><![CDATA[Prakash Chandran]]></dc:creator>
            <pubDate>Tue, 06 Oct 2026 14:55:47 GMT</pubDate>
            <content:encoded><![CDATA[<p>Hello Xano Developers!</p><p>At the end of Q2, we talked about how quickly AI is changing software development. Three months later, that shift is only accelerating.</p><p>It has never been easier to build software. AI can generate an application, write an API, and connect a database in minutes. Building is quickly becoming a commodity. Soon there will be more code than anyone can review line by line.</p><p>But building the first version is only the beginning.</p><p>The harder questions come as the software starts to matter and more people work on it. How do you understand what AI built? How do several people and agents work on it under the same rules? And how do you move it into production, next to the systems you already run?</p><p>Most platforms answer with parts. A database here, a runtime there, and the assembly is left to you.</p><p>Xano takes the other path. It is <strong>one platform to build, run and govern AI-built software</strong>, and our job is to make the hard decisions for you: how changes get reviewed, and how they reach production. You keep building fast. Your whole team can understand what was built and trust it.</p><p>That is where we're putting our focus: getting what you build into production, and keeping it trusted once it's there.</p><p>In Q3, we made some of our biggest progress yet toward that vision.</p><h2 id="c7b1dc8b-84d3-4cba-9b90-bb5557910c68" data-toc-id="c7b1dc8b-84d3-4cba-9b90-bb5557910c68" class="text-xl"><strong>From AI-assisted building to a shared way of building</strong></h2><p>AI agents are becoming part of the development team. But giving everyone an AI coding tool doesn't automatically mean they're building the same way.</p><p>With<a href="https://community.xano.com/product-updates/post/xano-2-5-update-waH0V59WCAGgcpD" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered"> <strong><u>Xano Knowledge</u></strong></a>, teams can now define the rules, documentation, and repeatable skills they want agents to follow once, and ensure that context is used by everyone.</p><p>Your workspace can carry persistent instructions through <a href="http://AGENTS.md" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered"><strong>AGENTS.md</strong></a>, refer to documentation that agents can pull in when needed, and <strong>Skills</strong> that define how your team performs specific tasks. That same context works with the Xano Agent and with external coding agents through the CLI and Developer MCP.</p><p>More importantly, that knowledge belongs to the workspace, not an individual developer's laptop or AI session. It can be reviewed, versioned, and controlled by admins just like the rest of your application.</p><p>As more software is built by agents, we think this becomes increasingly important: <strong>the way your team builds should belong to your team.</strong></p><h2 id="9439fd48-2425-45c8-a50e-f88db4b39c47" data-toc-id="9439fd48-2425-45c8-a50e-f88db4b39c47" class="text-xl"><strong>A more complete development lifecycle</strong></h2><p>We also continued expanding where and how developers can work with Xano.</p><p>In Q2, the CLI and Developer MCP opened Xano to external development workflows. In Q3, we extended that workflow to more of the application.</p><p>With<a href="https://community.xano.com/product-updates/post/xano-2-5-update-waH0V59WCAGgcpD" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered"> <strong><u>Static Frontend Hosting through the CLI and MCP</u></strong></a>, developers and agents can pull, push, and deploy static frontends alongside their backend, making it possible to work across more of an application from tools like Claude Code and Cursor without breaking the Xano development and deployment flow.</p><p>We also expanded<a href="https://community.xano.com/product-updates/post/xano-2-6-build-more-in-xano-ship-with-confidence-8wEIkEQnczNIXID" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered"> <strong><u>Sandbox environments</u></strong></a> so developers and AI agents can create temporary environments across multiple branches and work in parallel without interfering with each other. Changes can be built and tested in isolation before they move forward.</p><p>The direction here is simple: the faster software gets created, the more important it becomes to give every change a safe place to exist before it reaches production.</p><h2 id="b7ac8502-be82-4822-9d39-7f18b1b89e6a" data-toc-id="b7ac8502-be82-4822-9d39-7f18b1b89e6a" class="text-xl"><strong>Modernize without starting over</strong></h2><p>Not every application starts from scratch.</p><p>Some of the most important software our customers run today has been built over years, across different languages, services, vendors, and architectures. Replacing all of it rarely makes sense.</p><p>With<a href="https://community.xano.com/product-updates/post/xano-2-6-build-more-in-xano-ship-with-confidence-8wEIkEQnczNIXID" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered"> <strong><u>Microservices</u></strong></a>, teams can now bring existing Docker containers and Helm charts into Xano and call them directly from the Xano function stack. Those services can be monitored from the workspace and included in releases alongside the rest of the Xano application.</p><p>That means adopting Xano doesn't have to start with a rewrite.</p><p>A team can keep the services that already work, build new APIs and business logic around them, and modernize incrementally. Existing and new software can move through the same release process instead of creating another disconnected stack to operate.</p><p>That matters because a platform for AI-built software can't only work for what AI creates tomorrow. It also has to work with the systems your business depends on today.</p><h2 id="109d0770-eb54-4f35-9741-a82e53c107e5" data-toc-id="109d0770-eb54-4f35-9741-a82e53c107e5" class="text-xl"><strong>More control over what reaches production</strong></h2><p>We made significant progress this quarter on the other side of building: running software in production.</p><p><a href="https://community.xano.com/product-updates/post/xano-2-6-build-more-in-xano-ship-with-confidence-8wEIkEQnczNIXID" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered"><strong><u>Realtime v2</u></strong></a> brings more of the Xano development lifecycle to realtime applications, including authentication and authorization logic, payload validation, branches, Sandbox review, version history, RBAC, Request History, debugging, and rollback.</p><p>Teams can now treat realtime logic much more like the rest of their backend instead of operating it as a separate system.</p><p><a href="https://community.xano.com/product-updates/post/xano-2-6-build-more-in-xano-ship-with-confidence-8wEIkEQnczNIXID" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered"><strong><u>Testing</u></strong></a> also became easier to understand and act on. Test results now persist, run states are clearer, failures explain more about what went wrong, and the Agent can help create and debug tests.</p><p>And underneath all of this, we<a href="https://community.xano.com/product-updates/post/xano-2-6-build-more-in-xano-ship-with-confidence-8wEIkEQnczNIXID" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered"> <strong><u>re-platformed Xano's request execution engine</u></strong></a> to deliver lower latency, more throughput per instance, and steadier performance under load without requiring customers to change their applications.</p><p>These aren't isolated improvements. They're part of the same idea: <strong>building quickly only matters if teams can build together, and confidently run what they build.</strong></p><h2 id="b8f96765-c160-4e3f-b3c2-3626d9bcdd8d" data-toc-id="b8f96765-c160-4e3f-b3c2-3626d9bcdd8d" class="text-xl"><strong>Build with the AI infrastructure your team chooses</strong></h2><p>The AI ecosystem is moving too quickly for teams to be locked into a single model or provider.</p><p>In Q3, we<a href="https://community.xano.com/product-updates/post/xano-2-6-build-more-in-xano-ship-with-confidence-8wEIkEQnczNIXID" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered"> <strong><u>expanded AI provider support</u></strong></a> to include <strong>OpenRouter, AWS Bedrock, LiteLLM, and Azure Foundry</strong>, giving teams more flexibility to use approved models and existing AI infrastructure with Xano Agent and Agents.</p><p>For individual developers, model choice is often a preference. For teams, it can also be a question of security, cost, infrastructure, and organizational policy.</p><p>Xano should fit into those decisions rather than force teams around them.</p><h2 id="aba27c5b-0f5d-48bc-b502-06e68c7fa967" data-toc-id="aba27c5b-0f5d-48bc-b502-06e68c7fa967" class="text-xl"><strong>The bigger picture</strong></h2><p>Stepping back, the most important thing about Q3 isn't any single feature.</p><p>It's how the pieces work together.</p><p>A developer or AI agent can build in the tools they prefer. The team's knowledge and standards can follow them. Multiple builders can work safely in isolated environments. Existing services can become part of the application instead of being rewritten. Tests help validate what changed. Releases create a deliberate path into production. And once software is running, Xano gives the team a shared place to understand and operate it.</p><p>That is increasingly what we believe teams need from a backend platform in an AI-first development world.</p><p>The ability to generate software will continue getting cheaper and faster. The difficult part will be turning what gets generated into software a team can understand, operate, and confidently put in front of customers.</p><p>That's the problem we're building Xano to solve.</p><p>Thank you to everyone who built with us, tested these releases, reported issues, and pushed us throughout Q3. Your feedback continues to shape where the platform goes next.</p><p>We're excited about what these pieces make possible.</p><p>More soon. 🚀</p><p>Prakash</p>]]></content:encoded>
        </item>
    </channel>
</rss>