Planwise is a Themeatos Hub child product that turns client briefs into phases, milestones, sprints, and tasks inside WordPress. It includes New Plan, Ask AI with task citations, schedule views, and project integrations — without renting another SaaS workspace.

Does Planwise require Themeatos Hub?

Yes. Planwise installs through Themeatos Hub. Hub handles licensing, updates, routes such as /app and /login, branding, PWA options, and site-level AI provider settings.

Where are AI API keys stored?

Your keys stay on your WordPress site. Choose OpenAI, Claude, Gemini, Grok, or a custom OpenAI-compatible server in Hub settings. Planwise does not resell model tokens as a hosted AI markup layer.

How is Planwise different from hosted project tools?

Planwise runs on your WordPress install under Themeatos Hub. You keep domain, branding, data, and AI provider choice — instead of moving delivery work into a separate rented SaaS tab.

How long does it take to launch?

Teams that already use Themeatos Hub can typically install Planwise, configure routes and AI, and open New Plan within about a week — faster than building a custom workspace or vibe-coding a fragile prototype.

Which AI providers are supported?

OpenAI, Claude (Anthropic), Gemini, Grok, and custom OpenAI-compatible endpoints. Switch providers in Hub without changing your project data model.

Which integrations does Planwise include?

Project-level connections for GitHub (repos and issue signals), Google Drive (briefs and assets), and Telegram (secured group alerts). Site credentials are configured in Hub; per-project links live in the app.

Who owns the project data?

Project and task data live in your WordPress database on your hosting. You control backups, access, and uninstall options through Hub and WordPress — including keep-data flows when removing the product.

Can I use Ask AI on live project work?

Yes. Ask AI answers are grounded in the current project and can cite live tasks — useful for overdue work, blockers, and next focus without leaving the workspace.

How is Planwise licensed?

Planwise is distributed as a Themeatos Hub product entitlement. Pricing and purchase options are published on Themeatos; the landing schema does not advertise a free price unless a public free tier is offered.

Hub configuration

Open Themeatos → Planwise to configure the product.

Routes

Setting	Default	Purpose
App route slug	`app`	Frontend shell (`/app/`, `/app/projects/`, …)
Login route slug	`login`	Branded login page

Authentication

Built-in login — WordPress credentials on /login/ (can be disabled for custom auth).
Required capability — minimum capability after sign-in (default manage_options).
Allowed roles — optional allow-list; leave empty to allow any role that meets the capability.

Branding

Primary color, accent color, and Google Font family for the app shell. The logo uses the WordPress custom logo when set.

PWA

Enable/disable the progressive web app, name, short name, description, icon, and colors. Manifest and service worker URLs appear under Live URLs.

Notifications

In-app notifications, optional web push / iOS push credentials, prompt-on-login, and which event types are enabled.

Integrations

Hub cards for GitHub, Google Drive, and Telegram (bot token and webhook secret). Project-level connections are managed inside the app under a project’s Integrations tab.

When a bot token is saved, Planwise requires a webhook secret. If you leave the secret blank on first save, one is generated automatically. Inbound webhooks without a valid X-Telegram-Bot-Api-Secret-Token are rejected.

Data on uninstall

Under Data & uninstall, enable Keep Planwise data when uninstalling to retain settings, projects, tasks, and related meta after the plugin is removed.

If that option is off, uninstall removes Planwise options, notification table rows, custom post types (projects, tasks, schedule, activity, comments), and Planwise user meta (plan history, copilot chats, OAuth tokens, web-push subscription).