--- title: "About — RevCon" description: "Why RevCon exists, what is real vs. demo today, the design philosophy behind it, the tech stack, and how heavily every feature is tested before it ships." canonical_url: "https://revcon-demo.krisnatha.com/about" meta: "og:description": "Why RevCon exists, what is real vs. demo today, the design philosophy behind it, the tech stack, and how heavily every feature is tested before it ships." "og:title": "About RevCon" --- **About** # **A revenue console built around a daily habit, not a login screen. ** The numbers a revenue manager needs — pace, pickup, same-time-last-year, forecast — are usually scattered across a PMS, a spreadsheet and a rate-shopping tool. RevCon puts them in one place, fast enough to check before coffee, and scoped from day one for a single hotel or an entire chain. ## **What's real today** - Every feature on the Features page is built: the revenue system, all five intelligence layers, the AI assistant, the what-if simulator and the onboarding wizard. - The connector architecture is real and PMS-agnostic: a mock Oracle Opera connector today, a real one next, without changing revenue logic. - Automated tests cover revenue logic, connectors, permissions and performance — see below. ## **What's demo today** - The hotel chain is fictional: a resort plus two smaller properties, with two years of generated history and twelve months of forward bookings. - Competitor rates and demand events are simulated, so every screen has something realistic to show before a live rate-shopping feed is connected. - Real Oracle Opera access requires Oracle's partner program; pricing and plan tiers are intentionally undecided until closer to launch. **Design philosophy** ## **Minimal by default, numbers first.** Few colors, plenty of white space. Color is reserved for what needs attention — behind last year, high occupancy, negative pickup — not decoration. Pace and report tables stay compact and scannable, and the same chart style repeats across pace, booking curves, forecast and portfolio views, so nothing has to be relearned. **76.4%** **Ink** text · this year **70.2%** **Slate** last year **74.0%** **Amber** budget **+6.2 pts** **Emerald** ahead **−9 pts** **Rose** behind **Demo** **Teal** brand · CTA **Tech stack** ## **Chosen for the problem, not the trend.**
**Backend**
**Python, FastAPI**
Best data and statistics libraries for forecasting, pace and pricing.
**Background jobs**
**Celery on Redis**
Nightly syncs and heavy reports run outside web requests, many hotels in parallel; Redis also caches reports and portfolio roll-ups.
**Database**
**PostgreSQL**
Concurrent writes from many hotels, row-level security per hotel, and a fast-growing append-only history.
**Frontend**
**Vue 3, TypeScript, Vite**
The same stack as the current console, so interface logic carries over.
**Testing** ## **Every feature ships with automated tests.** Tests run on every code change before it can be merged — the thing that lets a small team change pricing logic without breaking last year's reports. ci · pull requestall checks **Revenue logic** Pace, pickup, STLY, forecast, budget variance, pricing and what-if, checked against hand-calculated numbers on fixed datasets. **Connectors** The mock Opera API and manual uploads, including amended/cancelled bookings, unmapped codes and failed syncs. **Security and permissions** One organization can never see another's data; every role sees and edits only what it should, including SSO, two-factor and MCP access. **Performance** Main screens stay under one second on a generated 50-hotel, 3-year chain; the build fails if a speed target is missed. **Reports** Daily, weekly and monthly reports are checked against the same numbers shown in the app. **Continuous integration** Every pull request runs the full suite; a failing test blocks the merge. ## **Want the detail behind any of this?** Request a demo and we'll walk through the parts that matter most to your property — connector mapping, forecast accuracy, or the AI assistant. [**Request a demo **](https://revcon-demo.krisnatha.com/contact) ## Sitemap See the full [sitemap](/sitemap.md) for all pages.