> ## Documentation Index
> Fetch the complete documentation index at: https://zite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What can I build with Zite?

> Learn which types of apps are a good fit for Zite, and when another product may be better.

## Overview

Zite is best for business apps, internal tools, dashboards, portals, and operational workflows that help a team collect, review, move, or act on information.

It is not designed for building a full SaaS company, consumer social app, public marketplace, or high-scale product where you need complete control over infrastructure, application code, billing, and production engineering.

<Check>
  A good rule of thumb: if the app helps a business improve their internal processes, Zite is likely a strong fit.
</Check>

## Best fits

Use Zite when you want to quickly build tools for a team, client, or business workflow.

<CardGroup cols={2}>
  <Card title="Internal tools" icon="screwdriver-wrench" iconType="regular" color="#FFC738">
    Admin panels, approval queues, inventory trackers, request managers, and tools your team uses to get work done.
  </Card>

  <Card title="Business dashboards" icon="chart-line" iconType="regular" color="#FFC738">
    Reporting views, KPI dashboards, pipeline trackers, customer summaries, and operational snapshots.
  </Card>

  <Card title="Client portals" icon="users" iconType="regular" color="#FFC738">
    Secure portals for clients, vendors, partners, or members to view information and submit updates.
  </Card>

  <Card title="Workflow apps" icon="diagram-project" iconType="regular" color="#FFC738">
    Apps that collect data, send notifications, update records, trigger integrations, or route work between people.
  </Card>
</CardGroup>

## Data sources

Zite works well when your app is connected to business data. You can use [Zite Database](/help/database/overview), [Airtable](/help/integrations/airtable), [Google Sheets](/help/integrations/google-sheets), or other business tools like Salesforce as the source behind your app.

These sources are a good fit for apps that need to view records, update statuses, collect submissions, trigger workflows, or give teams a cleaner interface for working with operational data.

## Common examples

* A CRM for tracking leads, customers, notes, and next steps
* A support dashboard for reviewing requests and assigning follow-ups
* A field operations tool for logging visits, photos, and status updates
* A client onboarding portal with forms, checklists, and document links
* A finance or HR approval app for requests, reviews, and notifications
* A database-backed dashboard for monitoring project, sales, or inventory data

## Less suitable

Zite is usually not the right starting point when the app itself is the product you plan to sell at scale.

<AccordionGroup>
  <Accordion title="SaaS products">
    Zite can help prototype a SaaS idea, but it is not intended to replace a dedicated engineering stack for subscription billing, multi-tenant infrastructure, product analytics, observability, release management, and custom backend systems.
  </Accordion>

  <Accordion title="Consumer apps">
    Zite is not optimized for social networks, creator platforms, games, public communities, dating apps, or other consumer products that depend on viral growth loops, high-volume traffic, app-store distribution, or deeply custom user experiences.
  </Accordion>

  <Accordion title="Native mobile apps">
    Zite does not support building native iOS or Android apps. Zite apps are web-based and can be shared by link, embedded, or used on mobile browsers.
  </Accordion>

  <Accordion title="Highly custom engineering projects">
    If you need full source-code ownership, custom hosting, complex realtime systems, or strict infrastructure control, a traditional development workflow may be a better fit.
  </Accordion>
</AccordionGroup>

<Info>
  You can still use Zite to prototype these ideas, validate workflows, create demos, or build admin tools around a larger product.
</Info>

## How to decide

Ask these questions before you start building:

* Who will use this app: a business team, a client, or the general public?
* Does the app support an existing process, or is the app the main product?
* Do you need integrations, forms, databases, dashboards, approvals, or notifications?
* Would launching a useful version quickly matter more than owning every technical detail?

If most answers point to business operations, internal use, or client-facing workflows, Zite is probably a good fit.

<p className="zite-related-topics-heading">Related topics</p>

<div className="zite-related-topics">
  <a href="/help/platform/how-to-build/creating-an-app">Create an app</a>
  <a href="/help/platform/workflows/overview">Workflows</a>
  <a href="/help/platform/access/share-to-web">Share to web</a>
</div>