Frequently asked questions

Yes, and security is built into the design: • Every project runs in its own isolated environment; your projects never share files with anyone else's. • Your projects are private by default; nobody can access them unless you invite them from the "Share" tab. • Your secret keys are stored in a separate secrets vault, exposed to your project as environment variables, and never appear in the chat. • You can connect your own GitHub repository and keep a full copy of the code with you at any time.

Only you, and anyone you explicitly invite. Projects are private by default. From "Share" you can add members by email or name, but be careful: a member gets full access to the project, including its secrets, so only add people you trust.

No. Keys are stored on the "Secrets" page and read from environment variables at runtime. The golden rule: never type a key inside the chat. Put it in Secrets only, so it stays out of the chat history and out of the code.

Yes, your project and its code are yours. You can keep a full copy at any time by connecting GitHub or downloading from the terminal, and move it wherever you like. Note: policy details and legal compliance (such as data protection) are governed by the official terms from the Uttra team.

SaaS (short for "Software as a Service") means ready-made software you pay a monthly subscription for, and you remain a "tenant" forever: stop paying and everything stops, and you own nothing. With Uttra you build the tool you want and own it yourself: the code is yours, you host it on your own domain, and you are not tied to anyone's subscription.

Instead of paying a software agency or subscribing to expensive ready-made tools, you build your own solutions with a simple description in plain language: an online store, a dashboard, an internal tool, or a booking system. You save cost and time, and you stay in control of everything.

That is exactly the problem Uttra solves. Instead of quotes worth thousands of riyals and weeks of waiting, you describe your idea and see it running within minutes, then develop it step by step on a minimal budget where you only pay for what you use.

Instead of a full development cycle (design, coding, testing, deployment) that takes weeks and a large budget, you build a working version (a prototype) in the same session. The actual savings depend on the size of your project, but the idea is: you pay for usage, with no fixed subscriptions and no team salaries.

You truly own it: the code is yours, you export it to GitHub or download it, and you host it on your own domain. Uttra builds it for you, but it stays yours, not a subscription that ends when you stop paying.

To be honest, some specialised services (payment gateways, maps, messaging) are still best connected as a service through their API key. Uttra builds "your app" and puts it in your hands, then connects it to these services whenever you need them, so you get the best of both worlds.

Tools like Copilot and Cursor are assistants that write lines of code inside your editor, but you remain responsible for everything around them: setting up the environment, installing packages, running the server, and solving deployment problems. Uttra is a complete platform from idea to published product: • You write your request in plain language, and the pages, code, and server are built together. • The environment is ready (Node, databases, terminal) with no setup on your part. • Live preview, click-to-edit visual editing, then publishing with a direct link. In short: the editor helps you write code, while Uttra hands you a working, published product.

They all fall under the "AI-assisted app building" category, but the differences are fundamental. What sets Uttra apart: • An open coding environment for every language: Uttra is a real, complete development environment. You can install any language, framework, or tool you need (Node, Python, PHP, Go, databases, and more) through the terminal using the usual install commands. You are not restricted to predefined languages or templates the way some platforms impose. • An authentic Arabic experience (RTL, Arabic interface and content), which is a weak point for most competitors. • Visual editing by clicking elements directly in the preview, without opening the code. • Full control in one place: terminal, secrets, GitHub integration, task scheduling, and hosting and publishing with a direct link. • Multiple working modes (Code / Plan / Chat / Debug / Review) that suit beginners and professionals alike.

A general model (like ChatGPT/Claude) gives you text or a code snippet in a chat window, and you copy it, run it, and publish it yourself. Uttra is a complete building agent: it does not just give you code, it creates the project, runs it in a ready environment, previews it, fixes its errors, and hosts it on a live link. In other words, you get a working product, not text.

Because it cuts out all the tedious parts: • Prototypes in minutes instead of hours of setup. • Environment, database, and deployment ready to go, so you focus on your idea, not on repetitive boilerplate. • You keep developer-level control: terminal, manual code editing, and GitHub integration so you can continue in your own editor whenever you want. • Ideal for quick ideas, landing pages, dashboards, and internal tools.

A feature that lets you edit your site visually without opening the code. In the preview, click the pencil icon to enter edit mode, then click any element (a heading, paragraph, button, or an entire section). It gets selected and shown to you (with the percentage of the screen it covers), and you start editing it directly. Every change is applied immediately to your site's actual source.

The panel has two tabs: • Text: rewrite the element's text directly. • Style: full visual control, including text colour or a gradient background, size (from S to 2XL), alignment (right/centre/left), and the font from a set of ready-made fonts. After editing, click "Save Edit".

Select the element first, then type your instruction in plain language and it will be applied to that specific element, for example "make the font bigger", "change the colour to blue", or "make this section two columns". This way the edit is focused precisely on one part.

Select the element or section, then type an instruction like "delete this section" or "delete this element", and it is removed from your site right away, faster than searching through the code.

Yes. While the agent is working on your request, you can type the next one and it is added to the queue to be executed afterwards, so you do not have to wait for each step to finish before typing the next.

From the "Style" tab choose "Remove custom styling from this element" and it returns to its original look. Useful for experimenting safely.

Visual editing is faster for precise edits on a specific element (text, colour, size, deletion). The chat is better for big changes, changes that touch several parts, or changes that need logic and data connections.

Yes. From the "GitHub" tab in the project, connect your account with a Personal Access Token that has the repo scope, then push your project directly to your own repository and keep a full copy of the code.

Push is supported directly from the GitHub tab. Pulling or importing an existing repository can be done through the terminal using the usual git commands (git clone / git pull) inside the project environment; all git tools are available to you there.

Yes, the code is yours. You can push it to GitHub at any time, or download/copy it through the terminal. You are not locked into the platform.

Yes. Alongside chat requests and visual editing, you can open the terminal, edit files, and install packages directly. Uttra does not stop you from working as a developer.

Yes. Uttra supports building mobile apps (using React Native / Expo) that run on your real device through the Expo Go app by scanning a QR code. It also supports Progressive Web Apps (PWA) that can be installed on the home screen. Describe your idea and mention that you want a mobile app.

Yes. You can build a complete backend (an API, the link that connects your app to data and services) and use a database, from a simple SQLite file up to a database like PostgreSQL or MySQL when needed. The environment runs the server and the database together.

You can ask for whatever suits your project, from simple HTML/CSS/JS websites to React and Vite apps, Node.js/Express servers, and more. The environment can be extended by installing whatever you need.

Yes. Add the service key in "Secrets" and ask Uttra to connect it. Common names such as STRIPE_SECRET_KEY and OPENAI_API_KEY are ready to use, and the keys stay protected outside the chat.

Yes. Through the terminal you can install npm packages or system packages your project needs, exactly like a real development environment.

Click "Publish" and the project becomes "Public", and you get a direct link to share with anyone, with no hosting setup on your part. You can publish on a free subdomain such as your-app.uttra.io, or on your own domain.

Yes, and a custom domain is free with every plan. On the "Publish" screen choose "Custom domain", enter your domain (for example app.example.com), then add the DNS records Uttra shows you in your domain registrar's panel (usually a TXT record for verification and an A record) and click "Verify domain". Once the settings propagate, your site is live on your domain.

Yes. Published sites run on your plan's resources (CPU, memory, and storage), which are distributed automatically across your published projects, so you do not need to set up a server. The higher your plan, the more resources are available to your sites.

Yes. You can publish several projects and share your plan's resources between them. Each published site automatically gets its share of CPU, memory, and storage.

To be honest, so your expectations stay realistic: • It is not a replacement for a full engineering team on massive, highly complex products; it is strongest at prototypes, websites, tools, and dashboards. • The clearer your request, the more accurate the result. Vague requests give vague results. • It does not replace your own review: review the code and the result before relying on it in sensitive production. • Paid features (such as team seats) depend on your plan.

Start from inside the platform: use Chat mode for advice without making changes, and Debug mode to diagnose an error. "Saved suggestions" also give you ready next steps. For general questions, this page and the tutorials guide are your first reference.

Yes. You can use Debug mode to diagnose and fix a problem, and Review mode to review and improve what has been built. Uttra also usually detects and fixes errors while building.

• Code: executes your request directly. • Plan: plans the steps before executing. • Chat: discussion and advice without changing the code. • Auto: picks the most suitable mode (recommended for beginners). • Debug: for fixing an error. • Review: for reviewing and improving existing work.

Yes. From "Scheduling" you can have Uttra run a task at a later time or repeat it periodically (a daily report, an update, a reminder), and it runs even while you are outside the app.

No. It is enough to describe your idea in plain language. The clearer and more precise your description, the closer the result will be to what you imagined. Professionals benefit from the terminal and manual editing, but they are not required.

Every request you send deducts an amount from your credits according to the size of the task, and the cost is shown next to each message. Clear, concise requests save your credits.

Click "Add credits" to top up and continue building. Your published projects and your code stay exactly as they are.

Yes. The "Consolidated team billing" option charges each member's usage on the project, and it is available within the Studio plan (multiple seats).

The best approach: start a small project and try building and previewing it yourself to see the result before scaling up. Plan and pricing details, and any trial credits, are governed by the official Uttra page, since they may change.