Riku AI
Riku AI is a no-code platform for building chat, form, vision and image AI apps on more than 40 large language models, then publishing them as shareable links, embedded widgets or team portals.
What is Riku AI?
Riku AI is a no-code platform for building, deploying and sharing AI applications. Rather than a single assistant, it hands you a builder: you pick one of four app types — chat, form, vision or image — write your instructions in plain English, and publish the result.
Its defining trait is breadth of model access. Riku fronts more than 40 large language models from nine providers, each documented on its own page: OpenAI (GPT-5, GPT-4o, the o-series and GPT-4o mini), Anthropic (Claude Opus, Sonnet and Haiku 4.5), Google (Gemini 3 Pro, 2.5 Pro, 2.5 Flash and the open Gemma family), Meta (Llama 4, 3.3 70B and 3.1 405B), xAI (Grok 4 and Grok 3), Groq's LPU-served open models, DeepSeek V3 and R1, Alibaba's Qwen family and AI21 Labs' Jamba models. No provider account or API key is needed, and models can be swapped at any point, so one prompt can be tested side by side and the winner deployed. Selected open-source models are included at no extra cost, and bring-your-own-key is available for teams wanting direct control.
Three products sit on the builder. App Builder creates the agents. Public App deploys them to a shareable URL with a custom slug, optional password protection and a ready-made iframe snippet. Workforce Portal groups several apps into a role- or department-specific workspace. Around them are six features: integrations with Zapier, Make, Pabbly and Google Sheets; Wizlay action agents for real-world tasks; custom styling with brand colours, logos and presets; embedded iframes; a Vectorize-backed knowledge base using retrieval-augmented generation; and white-label custom domains still marked Coming Soon.
A unified API returns normalised responses across every model through one endpoint, and that is where Riku directs heavy automation — the fair-usage policy restricts robot-driven traffic inside the web app itself. The platform grew out of a central playground for swapping models and storing prompts, and that playground remains part of the workflow. Riku claims more than 5,000 people building with it. Documentation sits on a separate site, with video guides on YouTube.
What it does
- Build chat, form, vision and image AI agents without writing code
- Run the same prompt across 40+ models from nine providers and keep whichever performs best
- Publish an app to a shareable URL with a custom slug and optional password protection
- Ground chat apps in your own documentation through a Vectorize knowledge base
- Embed any app into an existing website or CMS with a generated iframe snippet
- Trigger real-world tasks by connecting a Wizlay action agent
- Automate workflows through Zapier, Make, Pabbly, Google Sheets, webhooks or the unified API
When to use Riku AI / When not to
A quick filter to help you decide if Riku AI is the right fit.
When to use Riku AI
- Small marketing and content teams that need campaign ideas, on-brand copy and visuals without hiring a developer
- Customer support teams standardising replies through reusable chat and form apps
- Solo founders, freelancers and consultants assembling their own AI workforce on a single subscription
- Real estate agents and e-commerce sellers turning photographs into listings, product mockups and descriptions
- Operations and office managers automating receipt capture, expense records and repetitive document work
When not to use Riku AI
- Organisations with strict compliance requirements: there is no GDPR statement, no data processing agreement, no subprocessor list and no declared hosting country
- Teams that need a permanent free tier, since only two paid plans exist behind a five-day trial and refunds are excluded
- Mobile-first users, as no iOS or Android application is offered and everything runs in the browser
- High-volume automated workloads inside the web app, which the fair-usage policy restricts and redirects to the API
- Buyers who need to know whether their prompts and documents train the underlying models, a question the site never answers
How to use Riku AI
A typical end-to-end flow, from setup to results.
- Create an account and sign in to the Riku web application
- Open App Builder and choose an app type: chat, form, vision or image
- Select a model from the dropdown of 40+ LLMs, or supply your own provider key
- Write the prompt in plain English and add relevant examples in the playground
- Run the same prompt on several models side by side and weigh quality against cost
- Optionally connect a Vectorize knowledge base so a chat app answers from your own documents
- Optionally enter a Wizlay cluster and API key to trigger real-world actions
- Apply your brand colours, logo and styling, or start from one of the ready-made presets
- Publish the app to obtain a unique slug and shareable URL, adding a password if it should stay private
- Embed it with the generated iframe code, group it into a Workforce Portal, or wire it to Zapier, Make, Pabbly, Google Sheets or webhooks
Pros & Cons
Pros
- Forty-plus models from nine providers behind one interface, with no provider account or API key to manage
- Side-by-side comparison of the same prompt across models before you commit to one
- The entire path from prompt to published application requires no code
- Apps deploy to a shareable URL and embed into any site or CMS with a copy-paste iframe
- A single API endpoint normalises responses across every model available
- Team portals and subaccounts let several people share the same set of apps
- Low entry price for the breadth covered, with a five-day trial and free open-source models included
Cons
- No permanent free plan: two paid tiers behind a five-day trial, with refunds explicitly excluded
- The privacy notice dates from January 2022, was produced with a template generator, and publishes only the summary of eight of its thirteen sections
- Nothing on the site says whether customer data trains the models, and no opt-out is documented
- No GDPR statement, no data processing agreement, no subprocessor list and no declared hosting country
- No support email address is published; contact runs through a web form and the documentation site
- The knowledge base is limited to chat apps and a single provider, and white-label custom domains remain unreleased
- No native mobile application, and extra users and domains carry separate monthly charges
Pricing & Plans
Riku AI does not offer a permanent free plan. Two paid subscriptions are published: Pro Builder at USD 29.00 per month and Advanced Builder at USD 49.00 per month, each also available annually at USD 290 and USD 490 respectively. All plans open with a five-day free trial, and selected open-source models may be used at no additional cost. Subscriptions are non-refundable; cancellation takes effect immediately and stops any further charge.
- build AI agents (form
- chat
- vision
- image)
- BYOK for full control
- API integration
- free open-source models
- customise brand and feel
- everything in Pro Builder
- plus 2 additional subaccounts
- extra users at +$15/month
- 10 custom domains
- additional domains at +$5/domain/month
- webhook triggers
- Five-day free trial included on all plans
Data, GDPR & hosting
A consolidated view of how Riku AI handles your data.
GDPR overview
Implementation is minimal and largely undocumented. The acronym GDPR appears nowhere on the site. The privacy notice — last updated 14 January 2022 and generated with Termly — carries a single European reference, noting that in some regions such as the European Economic Area users hold rights giving greater access to and control over their personal information. A Data Protection Officer is named and reachable, and section 13 offers access, correction and deletion on request with a 30-day response. Legal bases are cited only generically: legitimate interests, performance of a contract, consent and legal obligations. There is no Article 27 representative, no data processing agreement, no subprocessor list and no transfer mechanism. Eight of the thirteen sections publish only their 'In Short' summary, so the substance behind most commitments is not actually online.
Who owns the data?
Riku's combined terms and privacy page never states who owns the prompts, documents or generated outputs, so ownership of the work produced on the platform is left undefined. What the privacy notice does describe is personal data: Riku collects names, email addresses and similar details you supply, plus automatically gathered technical information such as IP address, browser and device characteristics, operating system, device name, country, location and referring URLs. Payment data is not held by Riku at all — card numbers and security codes are stored by Stripe. Sharing is limited, in the vendor's own wording, to your consent, legal compliance, service delivery, protection of rights or business obligations. Questions go to the named Data Protection Officer.
Reuse rights
The terms are silent on reuse. There is no licence clause, no restriction on commercial exploitation and no claim over generated outputs, so nothing published on the site prevents you from using what you produce as you see fit. The only stated limits are behavioural: a fair-usage policy warns that heavy spamming of the product, or nonsense inputs, may lead to restricted access, and the unlimited open-source model allowance is explicitly conditioned on responsible, human use — robot-driven traffic inside the web application is disallowed and pushed towards the API instead. Apps you build can be published openly, protected by a password, or embedded on third-party websites.
Data retention & training
Hosting summary
Riku AI publishes no hosting information. Neither the terms nor the privacy notice names a hosting country, a region or an infrastructure provider for customer data. The only third party identified is Stripe, which stores payment card data; the privacy notice also states that Google Maps Platform APIs are used. The company itself is based in Singapore, at the postal address given on its legal page. On open-model providers, the site says only that Riku reaches them through vetted hosting infrastructure handled under its standard privacy terms, without naming a jurisdiction. Technical checks are no substitute: the domain resolves to a United States address operated by Amazon, but that address is an anycast node and reveals nothing about where application data is stored. The site's own backend calls, for the blog, contact form and newsletter, go to a Xano-hosted API. No standard contractual clauses or other international transfer mechanism is documented. In practice, anyone with a data residency requirement will have to ask the vendor directly.
Things to keep in mind
Risks and trade-offs to weigh before adopting Riku AI.
- Nothing on the site states whether prompts, uploaded documents or generated outputs feed model training, so that exposure cannot be assessed before committing
- No hosting country or region is declared; the company sits in Singapore while the domain resolves to a United States anycast node, which says nothing about where data actually lives
- Ownership of generated outputs is not addressed anywhere in the terms, leaving rights over your own work undefined
- Apps can be published openly, so forgetting to enable password protection may expose prompts, documents or internal information to anyone holding the link
- Subscriptions are non-refundable, which makes the five-day trial the only inexpensive moment to discover a poor fit
- Action agents can trigger real-world tasks automatically, and that needs review steps and hard limits before running unattended
- Handing customer replies, property descriptions or expense checks to a model erodes the in-house judgement that used to catch its mistakes
Setup & Integrations
Technical difficulty
Getting started is genuinely easy. You create an account, pick an app type, choose a model from a dropdown, write a prompt in plain English and publish — no installation, no provider keys, nothing to configure. The site's own framing, zero lines of code, matches what the pages show. Difficulty appears only in optional extras: pasting an iframe snippet into a page's HTML, pointing DNS at a custom domain, supplying a Wizlay cluster and API key, connecting a Vectorize knowledge base, or calling the unified API. None is required to build and share a working app.
Deployment
Integrations
Supported languages
Behind Riku AI
Social
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
Do I need to know how to code to use Riku AI?
How many AI models can I use?
Do I need my own API keys from OpenAI or Anthropic?
Is there a free plan?
Can I get a refund if the tool does not suit me?
How do I share an app I have built?
Can Riku answer from my own documents?
Is my data used to train the AI models?
Where is my data hosted?
How do I contact support?
Should you pick Riku AI?
Riku AI answers one question well: how do you put a working AI application in front of people without a developer, and without committing to a single model vendor? Its catalogue of more than 40 models across nine providers is genuinely broad for the price, and running one prompt against several of them before deploying is the kind of feature that saves real money at volume. The path from prompt to public URL, embedded iframe or team portal is short, and the unified API means the same work can be wired into Zapier, Make, Pabbly, Google Sheets or a webhook without rebuilding anything.
The reservations concern the paperwork rather than the product. The combined terms and privacy page dates from January 2022, was produced with a template generator, and publishes only the summary of eight of its thirteen sections. It never says who owns the outputs you create, never mentions the GDPR, offers no data processing agreement or subprocessor list, declares no hosting country, and is entirely silent on whether your prompts and documents train the underlying models. For a personal project or a small team that may be an acceptable trade; for anyone handling client or regulated data it is a list of questions to put to the vendor in writing before subscribing.
Pricing is straightforward — USD 29 or USD 49 per month, a five-day trial, no refunds — which concentrates the whole evaluation into a short window. Use it to test the models you actually intend to run, and to confirm the compliance points that matter to you. Riku AI is a capable builder wrapped in unusually light legal documentation, and both halves of that sentence deserve weight.
- Choosing a selection results in a full page refresh.
- Opens in a new window.