Availability
Feature availability
Check feature availability for your account and app before making it part of a pilot or production process.
Public guides describe supported customer paths. Some features depend on the plan, your organisation's rules or how Ahamo is set up for your organisation; the guide says so in an Availability note near the top.
Available now
| Area | Available |
|---|---|
| Building | Plans you build or dismiss, preview and visual editing, history and undo, images and media, files and folders, and what Ahamo knows and skills |
| Routines | Work on a schedule, in Library › Routines, with Active, Paused and Archived, each routine's page with its runs of the last 7 days and their logs, Run now, Cancel run, pause and archive, also by asking in the chat |
| APIs | APIs and scheduled jobs without screens, built in Python, with runs and requests in Analytics |
| Importing a repository | A GitHub repository into a new app, including apps built with other AI builders; a Supabase project in it can be connected and moved into Ahamo when you import or first publish |
| Connectors | Tools such as Notion, Slack, Stripe and Google, connected once, shared with your workspace, and used in your apps and in the chat; Ahamo and your organisation decide which connectors your workspace gets |
| Warehouses | BigQuery, Snowflake, Databricks, SQL Server (also on your own server), Azure SQL and Microsoft Fabric, where the connector is on for your workspace |
| Your data in the chat | Questions answered from your warehouse, with each figure's check shown |
| Dashboards | Charts, maps, numbers, tables and text from a chat, filters, live warehouse tiles, editing by hand, and a refresh schedule |
| Datasets | Access levels, row rules, column masks, totals-only access, requests for access, and datasets people can find |
| Payments | Checkout pages, payment links and subscriptions with your own Stripe account, through the Stripe connector, where it is available in your workspace |
| Data | Database, SQL console, restores of shared data to any minute in the last 30 days, back to the last publish that changed the database, exports, slow-query log |
| Sign-in for your app | Email and password, sign-in links, email confirmation, password reset, user management, Supabase sign-in |
| Live features | Live updates, live sessions, web push notifications |
| Files | Uploads, and your own S3 bucket for a published app |
| AI in your apps | Chat, structured answers, classification, search by meaning, images, speech, on workspace credits |
| Supabase | Your own Postgres (Pro and up), external tables, moving a project into Ahamo |
| Publishing | A security check before you publish, your own domain (Pro and up), staging (Pro and up), unpublish |
| Working together | Folders, roles and permissions (more roles on Pro and Team), live presence, team chat, and a Trash that keeps deleted apps for 30 days |
| Developers | Client SDK, server functions, secrets and variables, GitHub sync, external APIs |
| AI clients | Connecting Claude, Cursor or another MCP client; service credentials on Team |
Not available yet
These are planned. Don't make them part of a pilot or production process until a guide describes them:
- sign-in to your app with Google, Apple, Microsoft or GitHub;
- passkeys and authenticator apps for your app's users;
- sending other email from your app through Ahamo (use an email provider with a secret instead);
- publishing an app as an MCP server;
- turning an app into a workspace template that others start from;
- moving an app to another workspace;
- SCIM provisioning, and groups of members for roles other than dataset access;
- connecting Snowflake or Databricks from Ahamo's fixed address, for an account that allows only listed addresses;
- warehouses reachable only on a private network;
- Ahamo's fixed address in the Azure SQL and Microsoft Fabric connect dialogs (the SQL Server dialog shows it, and they use the same one);
- answers from a warehouse larger than 25 MB;
- signing in to Azure SQL or Fabric as each person, so statements run with their own rights;
- taking a dataset's rows out as a file with the Export setting of a grant.
Before committing to a feature
Check whether the required control is available in your workspace and whether the guide includes an availability note. If a capability is essential to your evaluation, confirm its availability with Ahamo before making a delivery commitment.
If your screen differs
Check the selected workspace, your access, the app, and the environment. A visible but unavailable control cannot necessarily be enabled through a prompt. Keep credentials out of prompts. Contact Ahamo if the documented path is unavailable to your account.