iVistaar

Like Render — for your intranet.

Publish Flask, Dash, Streamlit, and Gradio apps on your Windows Server as organization URLs. No public cloud. No Git required on the server.

Folder in. Org URL out.

Built for locked-down Windows shops where Render, Railway, and Heroku are not an option.

  1. 01

    Install on the server

    Unzip and run the service installer. Admin and apps stay on your box, behind your firewall.

  2. 02

    Connect a folder

    Point iVistaar at C:\Projects\your-app — or a reachable UNC path. No zip ritual.

  3. 03

    Share the URL

    Your team opens an internal site. Redeploy on demand — or let auto-deploy watch the folder.

Simple server pricing.

Try three sites free. When you’re ready for production, buy a clear yearly bundle — no opaque “contact sales” maze.

Free demo

$0

Up to 3 sites on one server

  • Full control plane install
  • Flask, Dash, FastAPI, Streamlit, Gradio
  • Events, rollback, health & logs
Download

Compared with enterprise “internal app portals” that often start in the mid–five figures, this is a deliberate mid-market price for one governed Windows Server. Questions: [email protected]

For IT & security

Answers buyers ask before a Windows Server install is approved.

Where does it run?
On your Windows Server. Code and traffic stay inside your network. No required SaaS control plane.
How do apps run?
Recommended mode: Waitress scheduled tasks under a service identity (default SYSTEM via the installer). Each app gets its own localhost port and task (iVistaarApp-<slug>), isolated from sibling apps’ processes.
Admin authentication
Password-protected admin UI. Change the first-run password under Account immediately. Windows Authentication / AD group gating for deployed apps is on the roadmap — today you place iVistaar behind your existing reverse proxy or VPN as you would any internal site.
Audit & operations
Deployments record events (actor, status, source mtime), release archives with rollback, plus live health, ports, and runtime logs in the admin UI.
Licensing
Free demo: 3 sites. Production: yearly SPC for the 10-site server bundle. Activate in the License page — no phone-home required for day-to-day deploys.

Why teams install it

Python apps get built constantly in enterprises — then die on localhost:8501 because IIS hosting is painful and public PaaS is blocked.

After you download

Do these on the Windows Server. First-run credentials are in the install guide — change them before wider exposure.

  1. 01

    Extract the zip

    Unzip to a permanent folder, for example C:\iVistaar or C:\software\ivistaar.

  2. 02

    Run the service installer

    Open PowerShell as Administrator, then:

    cd C:\iVistaar
    .\scripts\install-admin-service.cmd -Port 8080

    Prefer this over plain IIS hosting — gateway + Waitress for admin and apps (including Streamlit WebSockets).

  3. 03

    Sign in and secure the admin

    Open http://localhost:8080/, sign in with the first-run credentials from INSTALL.md, then use Account to set a new password.

  4. 04

    Connect a project folder

    Admin → Connect → folder path → Deploy. Open the URL under /apps/<slug>/. Use Health & runtime if something fails.

Install guide · INSTALL.md · Troubleshooting

Quick questions

Short answers for buyers and first installs. Deep Windows failure modes live in Troubleshooting.

Does code leave our network?

No. iVistaar runs on your Windows Server. Deploy from folders already on that server (or UNC paths you allow).

What stacks can we publish?

Flask, Dash, FastAPI, Streamlit, and Gradio under /apps/<slug>/. Prefer service mode for reliable hosting and Streamlit/Gradio WebSockets.

How does the free demo become paid?

Free includes 3 sites. For production, request a yearly SPC for the $9,000 / 10 sites / server bundle and activate it under License in the admin UI.

Fighting Event Viewer? Open troubleshooting (IIS 500s, Dash Loading, pandas wheels, Streamlit WebSockets, and more).

Get iVistaar

Download the Windows Server package. Your browser saves the zip, then this page jumps to After you download.

Requires Windows Server and Python 3.10+. Production-ready for intranet Windows shops. First-run credentials are documented in the install guide — change them under Account before broader exposure.