Plexara
Solutions
For Data Teams
Workflows
Built for Every Role
Analyst
- Discover data through semantic catalog search
- Understand context from enriched schema descriptions
- Query with federated SQL across all data sources
- Visualize results as interactive dashboards
- Save and share as versioned Portal assets
Engineer
- Trace lineage at dataset and column level
- Inspect data quality signals and incidents
- Manage metadata: descriptions, tags, glossary terms
- Create curated queries for repeatable patterns
- Build prompts for automated workflows
Steward
- Review captured insights from agent sessions
- Synthesize related insights into documentation
- Apply approved changes to the catalog
- Manage glossary terms and data products
- Track changeset history with rollback capability
Day-to-Day
Portal as Your Workspace
Assets, collections, prompts, and version history in one workspace. Organize work into collections for structured presentation: weekly analytics packages, quarterly board data, onboarding materials for new team members.
Prompts codify repeatable workflows at three scope levels. Global prompts are available to everyone. Persona prompts target specific roles. Personal prompts are private to the creator. Template arguments make prompts reusable across different datasets and topics.
The platform remembers your corrections, preferences, and context across sessions. Multi-strategy recall surfaces relevant prior knowledge automatically: entity lookup finds memories about specific datasets, semantic search finds conceptually related context, and graph traversal follows DataHub lineage to find connected knowledge.
Every correction you make and every insight you share gets captured. The next person who asks about the same dataset benefits from what you already figured out. Knowledge compounds instead of evaporating.
Common questions
For Data Teams FAQ
Analysts work in their AI client of choice (Claude, ChatGPT, Cursor) and reach the warehouse, catalog, and prior context through Plexara's MCP server. They write natural language; the agent calls Trino for queries, DataHub for definitions, and memory for what they learned last time. Results land as portal assets they can share or version.
Engineers get governed access to pipelines, lineage, and operational metadata through their persona. Stewards review and promote insights to catalog documentation, manage prompts and personas, and curate the knowledge layer. Both share a workspace with assets, collections, and version history.
Prompts codify repeatable workflows. Three scopes: global prompts for organization-wide patterns, persona prompts for role-specific routines, and personal prompts for an individual's habits. The agent surfaces them by name, so a teammate can use the same prompt and get the same workflow without copying instructions around.
An asset is a single artifact: a query result, a chart, an export, a generated document. A collection groups related assets into a workspace, with version history and shared comments. Together they replace the ad-hoc "send a CSV in Slack" pattern with persistent, governed work.
Yes. Plexara connects to your warehouse through Trino federation, so your BI tool keeps connecting the way it does today. Plexara adds the AI agent surface on top; analysts choose when to use the BI tool versus the agent based on the task.