Agentic AI Documentation
Enterprise-ready documentation for an agent orchestration and analytics platform built with Next.js, Go, Spring Boot, and ClickHouse.
Features
- Persistent ClickHouse DB schema for all entities
- REST APIs (30+ endpoints) for agents, tasks, workflows, analytics, notifications, audit, and runs
- Supervisor-to-Agent orchestration and real-time LLM execution (LangChain4j + Go)
- Real-time SSE notifications and analytics dashboards
- JWT authentication, role-based access, and secure credential storage
- Visual workflow editor, Kanban task manager, and agent manager
- Enterprise-grade audit logging and compliance support
Architecture
Application Layer
- Frontend: Next.js 14, React, Tailwind CSS
- API Service: Go 1.22 REST service
- LLM Service: Spring Boot 3.3.5 + LangChain4j
Platform Layer
- Database: ClickHouse 24.8 for analytics and runtime events
- Containerization: Docker Compose multi-service orchestration
- Security: JWT HS256, RBAC-ready model, .env secret management
Setup & Installation
- Clone repository and move to project root.
- Copy environment template from .env.example to .env and set secrets.
- Run docker compose up --build to bring up all services.
- Open web on port 3000, Go API on 8080, LLM service on 8081, ClickHouse on 8123.
Local Development
1. Start ClickHouse only.
2. Run Go API from services/go-api.
3. Run LangChain4j service from services/langchain4j-service.
4. Run Next.js app from apps/web.
Runtime Endpoints
Web UI
http://localhost:3000
Go API
http://localhost:8080
LangChain4j API
http://localhost:8081
ClickHouse HTTP
http://localhost:8123
How-To Guides
- Login with admin credentials and rotate password immediately after first login
- Manage agents from the Agents module (add, edit, delete, and version)
- Create and track work in Kanban or List task views
- Design multi-step orchestration in the visual workflow editor
- Track trends, token usage, and agent activity in Analytics
- Use Notification Center for real-time workflow and runtime updates
- Run LLM flows in Agent Chat Console and review outcomes in Audit tab
Admin & Security
All credentials are stored in .env (never hardcoded in source code).
JWT tokens expire in 24 hours and are validated via middleware.
ClickHouse and API passwords should never be exposed in URLs or logs.
Audit logs track key administrative and operational actions.
RBAC can be extended for multi-team or enterprise-level access separation.
Best Practices
- Change default admin credentials immediately.
- Backup ClickHouse data on a fixed schedule.
- Rotate JWT secrets and API keys periodically.
- Monitor analytics for unusual activity spikes.
- Enable SSO or OAuth for enterprise identity controls.
- Add CI/CD checks for quality and deployment reliability.
Product Editions
Basic
- Core agent orchestration
- Starter workflow automation
- Essential analytics dashboard
- Single-team operations
Professional
- Advanced orchestration controls
- Expanded workflow tooling
- Extended analytics and observability
- Team collaboration and governance
Enterprise
- Unlimited orchestration scale
- Enterprise security and compliance controls
- SSO/OAuth and custom RBAC extensions
- Dedicated operational support model
Industry Comparison
| Feature | Jagentic Network | Industry Standard |
|---|---|---|
| Agent orchestration | Yes | Partial/No |
| LLM integration | Yes (LangChain4j) | No/Plugin-based |
| Real-time analytics | Yes | Limited |
| ClickHouse backend | Yes | Rare |
| Visual workflow editor | Yes | Yes |
| Audit and compliance | Yes | Varies |
FAQ & Support
Where are credentials stored?
In .env configuration only; credentials should not be hardcoded or put in URLs.
How do I reset admin password?
Use database-level reset flow or API-driven admin password reset process.
How do I add new agent types?
Extend the Go API and frontend models, then expose orchestration mappings.
How can I export analytics?
Use the analytics dashboard exports or query ClickHouse directly.