AI Systems
niwas.ai / Propmatrix
AI-assisted real estate platform with backend architecture, mobile clients, and production-focused data flows.
Source platform: github
Display order: 1
Publicly visible from the showcase manager
Cross-Platform Systems
Product ecosystems shaped as one operating surface.
Inspired by the stronger storytelling rhythm of the reference site, this page reframes the portfolio around connected products, shared delivery layers, and backend-aware orchestration.
Route stats
Connected surfaces
4
GitHub, LinkedIn, Meta, and X normalized under one hub
Public showcase
3
Curated modules ready for the portfolio and menu system
Current status
Available for new work
Signals pulled from the internal portfolio data layer
Directory
Managed showcase
Projects
Backend-fed project stories curated from the unified public showcase layer.
Applied intelligence
AI Core
AI modules, context assembly, and workflow patterns tied to real portfolio operations.
Backend and admin
Platform Hub
Connectors, APIs, admin tools, and the system design that powers the public site.
Spotlight
What the ecosystem layer now enables
The portfolio can evolve like a product platform, not a static brochure.
Unified pages
4 route-backed modules
Showcase source
3 managed entries
Signals
4 connected channels
Operating Products
Core ecosystems and flagship workstreams
Each ecosystem below blends delivery, backend ownership, and a curated public surface instead of living as isolated one-off projects.
Open route
Enterprise Web
APS Admission Panel
High-traffic admissions workflow spanning web, mobile, and operational management tooling.
Source platform: linkedin
Display order: 2
Publicly visible from the showcase manager
Data Platform
Data Intelligence Engine
Security-minded data discovery, lineage tracking, and PII-aware enterprise architecture work.
Source platform: meta
Display order: 3
Publicly visible from the showcase manager
Delivery Layers
From public narrative to operator tooling
The site now behaves like a real system: public routes, admin control, synchronized content, and reusable data contracts.
Frontend
Public experience
The homepage and route pages render from internal portfolio data instead of direct browser-side third-party fetches.
Shared identity and showcase payloads
Route-backed navigation and focused page narratives
Graceful fallbacks when connectors are offline
Admin
Admin cockpit
Connections, sync logs, showcase ordering, and content review live in one protected area inside the same Next.js project.
Protected /admin area
Connector health and sync run visibility
Manual curation for public-facing modules
Backend
Backend services
MariaDB-backed records keep platform accounts, snapshots, content items, and showcase entries under one operational model.
Normalized storage across platforms
Server-side route handlers for public and admin APIs
Prepared for future scheduled syncs and automations
Connected Signals
Live channels feeding the ecosystem narrative
These channels can be used as public proof, content sources, and traffic entry points without scattering logic across the frontend.
Repos
GitHub
AI Systems Architect
Repos: 40
Synced into normalized internal models
Deep link available for public review
Route flow
How this module moves from concept to public output
Phase 01
Shape the ecosystem
Define products as connected modules instead of isolated portfolio cards.
Phase 02
Centralize operations
Push platform content and identity into one admin-backed delivery layer.
Phase 03
Publish with control
Choose what reaches the public site from a single showcase manager.