> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/release-notes/2026/april-20th-2026.md).

# April 20

Version: 2.7.0

This version strengthens the platform across **monetization**, **onboarding**, and **scalability**, while also introducing early capabilities for **mobile app creation**.\
Overall, this release moves the platform closer to being production-ready for real-world usage and growth.

{% hint style="info" %}
Some features are platform-enabled and will be visible only if configured for your workspace.
{% endhint %}

## Platform Refresh

A small change, big impact:

* **Updated Qore platform logo** - reflecting a more modern, product-ready identity

## Billing & Payments (Platform-enabled)

Enabling platforms to **monetize, manage subscriptions,** and t**rack usage** effectively:

* Credit exhaustion handling with notifications
* Automated invoicing and email delivery
* Branded Stripe checkout experience
* Plan activation email notifications enabled

## Onboarding & Access

Reducing friction in getting users started:

* First-time email verification and password setup
* Google SSO (passwordless login experience)

## Mobile App Builder (Beta)

Expanding platform capabilities beyond the web:

{% hint style="info" %}
Currently in Beta - you may experience occasional issues as we continue to stabilize and improve the experience.
{% endhint %}

* Native mobile app build & preview
* Mobile app package export (ZIP) - single package for Android & iOS (device-based); app store publishing not in scope

## Platform Reliability & Scale

Strengthening the system for **higher usage and enterprise readiness**:

* Enhanced observability with request logging improvements
* Database read replica support
* Simplified database migrations
* Vector store optimization for better performance

## Security Updates

Enhancing platform trust and resilience:

* Backend process sanitization improvements
* Vulnerability fixes across frontend and backend

With these updates, the Uptiq platform moves closer to enabling **seamless, production-grade app** and **agent development at scale**.

There’s more coming soon - keep building and sharing your feedback with us.

**Happy building!**

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.uptiq.ai/ai-workbench-qore/release-notes/2026/april-20th-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
