iVistaar
From localhost concept to a useful internal product.
Connect a project folder on your Windows Server. Deploy. Get an organization URL — without Git, without sending code outside your network.
Three steps. Then you’re live.
Built for locked-down Windows shops where Render and public PaaS aren’t an option.
-
01
Install on IIS
Unzip on the server and run the admin installer. No Git required on the machine.
-
02
Connect a folder
Point iVistaar at
C:\Projects\your-app— or a reachable UNC path. -
03
Share the URL
Your team opens an internal site. Redeploy when the code changes — or let auto-deploy watch for you.
Like Render — for your intranet.
One control plane for Flask, Dash, FastAPI, Streamlit, and Gradio apps that usually die on random localhost ports.
- Folder connect — no zip ritual, no external Git on the server
- Auto-deploy — watches Python sources and redeploys on change
- Events & rollback — deployment history with actor, mtime, and release archives
- Stays inside — runs on your IIS box, behind your firewall
Common deploy questions
Real issues from Windows installs — so you spend less time in Event Viewer.
IIS install returns HTTP 500 with empty logs
Use service mode instead: scripts\install-admin-service.cmd -Port 8080. HttpPlatformHandler often fails when Python lives under a user AppData folder.
pip fails on pandas (Meson / vswhere / Visual Studio)
There is no wheel for your Python version, so pip tried to compile from source. Prefer Python 3.11–3.12, or bump pins (e.g. pandas>=2.3.3 on 3.14). You should not need Visual Studio Build Tools.
Dash stuck on “Loading…” / DashRenderer is not defined
Asset URLs must be under /apps/<slug>/. Use entrypoint run:server (or app:server), set server = app.server, redeploy on a current release, then hard-refresh. iVistaar injects the public path prefix for you.
NameError: dash is not defined
You imported from dash import Dash but called dash.Dash(...). Use Dash(...), or add import dash.
Wrong entrypoint for Dash / “cannot import name app”
Dash needs the Flask server object: server = app.server and Connect entrypoint app:server or run:server matching your filename — not app:app unless that attribute is a WSGI app.
WinError 32 on runtime.log during redeploy
The app process still held the log file open. Current releases stop the app task before syncing. Stop iVistaarApp-<slug> and redeploy, or upgrade past 0.6.9.
Installer picks Python 2.7
Python 2.7 is not supported. Install Python 3.10+ and re-run the installer, or pass -PythonPath to install-admin-service.cmd.
Cannot add a fourth project
The free demo includes three projects. Activate a yearly SPC under License, or email [email protected].
Licensing — try it, then grow.
Install the full product. The free demo lets you run up to three sites. Need more? Unlock with a yearly subscription code.
-
01
Install everything
Download and install iVistaar on your Windows Server. You get the complete control plane — not a cut-down trial build.
-
02
Use three sites free
Connect and deploy up to three projects. Enough to prove the workflow with real apps on your intranet.
-
03
Unlock unlimited with SPC
When you need a fourth site, contact the iVistaar team for a yearly SPC (subscription product code). Paste it in the License page — unlimited projects until renewal.
Questions or ready for a license? [email protected]
Get iVistaar
Windows Server package with install guides. Extract to C:\iVistaar and run the installer. Free demo includes three sites.
Requires IIS, HttpPlatformHandler, and Python 3.10+. Default login is for first setup only — change it before wider exposure.