HASSAR.AI Platform

Final

All screens, features, and security measures — complete and live.

01

Landing & Auth

Home
Home
Login
Login
Register
Register — live password strength
02

Dashboard

Dashboard
My IoT Blueprint + Talk to Jim
03

Blueprint — Create → Review → Download

Blueprint hub
Create new / review existing
Home Setup
1 · Home Setup
Devices
2 · Devices
Network
3 · Network
Goals
4 · Goals
Review
5 · Review
Encrypt and download
Passphrase set client-side → encrypted .hassar file downloaded

Revision — "Other (custom)" on every choice field

Every chip/tile selection in the wizard (house type, rooms, brands, per-brand devices, network protocols, goals) now has an "+ Other" option to type a custom value, so the wizard never limits the customer to the preset list.

Other option in Home Setup
1 · Home Setup — custom house type + room
Other option in Devices
2 · Devices — custom brand + per-brand device
Other option in Network
3 · Network — custom protocol
Other option in Goals
4 · Goals — custom goal
04

Talk to Jim

Jim intro
Intro + pathway prompt
Jim pathway menu
AGIM-driven pathway menu
Blueprint loaded in chat
Blueprint decrypted in-browser, loaded as chat context
Session history
Multi-session chat history
05

Security

  • Blueprint encrypted client-side (AES-256-GCM, PBKDF2-SHA256, 390,000 iterations) — passphrase and plaintext never leave the browser
  • Server stores only a SHA-256 hash + file size for ownership — never blueprint content
  • JWT auth — short-lived access token + httpOnly refresh cookie
  • Account lockout after 5 failed logins (15 min)
  • Anti email-enumeration on registration
  • Rate limiting on all auth and chat endpoints
  • CORS allowlist — no wildcard origins
  • Role-gated admin routes (RBAC)
  • Non-root Docker container
  • Semgrep static scan — clean
  • Promptfoo LLM red-team — all jailbreak/PII/prompt-extraction attempts refused
06

Architecture & Integration

  • Frontend live — Next.js on Cloudflare Pages (hassar.ai)
  • Backend live — FastAPI, client's own server (backend.hassar.ai)
  • AGIM connected — api.hassar.ai routed correctly, Jim responding end-to-end
  • Behaviour rules live in AGIM's own system prompt; HASSAR.AI only forwards messages and blueprint context
  • HASSAR.AI fallback prompt kept minimal — only used if AGIM is offline