Only WordPress data: the posts Aiomatic generates and the meta keys it stamps on them (commonly _aiomatic_source_url, _openai_model, _aiomatic_run_id and similar), plus standard wp_posts columns like post_status, post_author and post_date. Cloud generations remain with the vendor; SleekView only surfaces what is already stored in WP.

No. SleekView never calls a model vendor. It reads posts and postmeta that Aiomatic has already written to your database. If a generation never reached WordPress, it cannot appear on the dashboard, which is the honest behaviour rather than a fabricated number.

Yes. Group a Pie or Bar card by the model meta key Aiomatic writes, typically _openai_model. The dashboard then shows the share of generations by model, which is useful for cost reviews and for deciding when to retire an older model from the default settings.

Yes. Group by post_date with an Area or Line card and pick a Count aggregation to see generations per day, week or month. Quarterly reviews use the trend to argue about cadence rather than guess at it.

Yes. Aiomatic's meta is written when the post is created, regardless of status. A Pie grouped by post_status shows the live split between draft, pending and published, which is exactly the surface editorial leads want when they ask "how much is queued?".

Yes. Add a filter for post_author and every card narrows to that author. Editorial leads use this for one-on-one reviews; ops uses it to plan handoffs when one author leans on the plugin more than the team realises.

Yes. Any filtered set behind a chart card exports as CSV with the same columns the table view would show. Useful for sharing a quarterly content briefing with an external editor or for archiving a snapshot before a clean-up sprint.

Yes. Aiomatic can be configured to write into any post type, and SleekView mirrors that. A site that generates standard posts, products and case studies can group its dashboard by post type or scope each card to a single type.