Everything about Plora.
Explore the platform, products, accounts, plans, technology and common troubleshooting steps. This guide is designed to be a public starting point for understanding the Plora ecosystem.
Plora at a glance
Plora is an AI platform built around a connected set of creative and productivity tools. Plora is the parent brand; Plora AI, Plora Paint and Plora Video are products within the ecosystem. The goal is to make it easier to move from an idea to written, visual and video work in one recognizable product family.
Creator and development
Plora was created and is developed by Ridwan Ahmed, Founder & Developer of Plora. Ridwan Ahmed is the creator and developer behind the Plora platform and its product family: Plora AI, Plora Paint, and Plora Video. The official creator profile is available at /about.
Products
Plora AI is the conversational AI experience for asking questions, exploring ideas and working with text. Plora Paint is the image and visual creation workspace. Plora Video is the video creation and editing experience. Each product has its own interface and deployment, while the main Plora website remains the central entry point.
Quick links: Image Generator · Log in · Create an account
Plora AI
Plora AI is the chat and text-focused product in the Plora family. It is intended to help with explanations, brainstorming, drafting, summarizing, and coding or problem-solving workflows. Product capabilities can change as development progresses. Plora is the product identity; do not assume that a particular third-party model powers every feature.
Plora Paint
Plora Paint focuses on image generation and visual work. The intended workflow is to create or open an image, make edits in the workspace, preview the result, and save or download the output where those controls are available. Paint uses the main Plora account sign-in rather than a separate Paint-only account page. If you are sent to sign in, complete sign-in on Plora and then return to Paint.
Plora Video
Plora Video is the dedicated video creation and editing product. It is deployed separately from the main Plora frontend. Open the product directly or use the link provided by the Plora website or dashboard. Editor availability depends on the deployed version and supported browser features.
Main website and navigation
The main Plora website introduces the ecosystem, explains product areas and pricing, and links to account and product experiences. Use the top navigation to explore the site, and use this documentation page as a reference. The /docs route is public documentation and should be reachable without signing in.
Accounts and sign-in
Create an account from the Register page or sign in from the Log In page. Google OAuth is used for dashboard sign-in. Product routes that rely on the main Plora account should send unauthenticated visitors through the main Plora sign-in flow and then return them to the intended destination when supported. Never share passwords, OAuth tokens, session cookies, or one-time codes.
Security and privacy
Plora's authentication and access controls are handled through its backend and configured frontend flows. The website has used Cloudflare Turnstile on relevant account forms. Security features and session policies can evolve, so consult the current sign-in experience for the active behavior. Do not place secret API keys in browser code or publish private credentials in support requests.
Plans and pricing
Plora currently offers one Free plan. There are no paid tiers or subscription upgrades. Every Plora account includes 5 GB of Plora Cloud storage. Some actions may use Plora credits; available credit rewards and purchase options are shown in the account experience.
See the live pricing section for the current offer.
Technology and deployment
The main frontend uses Next.js and React with TypeScript and SCSS/CSS. The frontend is hosted on Vercel and the backend is hosted on Render. Plora's products may be deployed as separate applications. Deployments can be updated independently, so a product's current availability may differ from another product's status.
Backend and service status
The frontend communicates with Plora's backend for supported server features. A system-status link may be available from the website footer. Public documentation does not expose private service credentials, internal environment variables, secret endpoints, or administrative access. If a feature fails, reload once, check the relevant product deployment, and report the page URL and a non-sensitive error message.
Troubleshooting
If a page is blank, reload it and try an up-to-date browser. If an editor cannot start, check whether the product deployment is healthy and whether browser permissions or supported media features are blocking it. If sign-in loops between a product and the dashboard, return to the main Plora login page and retry from the product link. Never send passwords, session cookies, access tokens or secret keys when reporting a bug.
Accessibility and browser support
Use a modern browser with JavaScript enabled for interactive product features. Some creation tools may need additional browser capabilities. Where available, prefer keyboard navigation, readable zoom levels and reduced-motion settings. If a control is inaccessible, report the page, browser and the action that failed.
Frequently asked questions
Is Plora one product? Plora is the parent platform with multiple products. Do I need a separate Paint account? Paint is intended to use the main Plora sign-in flow. Where are the docs? At /docs. What plan does Plora offer? Plora currently has one Free plan with 5 GB of Cloud storage per account. Some actions may use credits. Where do I report a problem? Use the available Plora support or feedback channel and include only non-sensitive diagnostic details.