Project planning
Phases, tasks and subtasks with a Gantt chart and dependencies. Assignments to employees and an hour model of estimated, planned and booked — so it becomes visible where plan and reality drift apart.
AI-assisted planning
You collect the tasks — Plainova proposes the plan: phases, dependencies, effort estimates and assignments, matched to your team’s skills and time off. You review and decide.
No credit card required. Free plan stays free.
AI
Planning is mostly legwork: sorting tasks, fixing the order, estimating effort, assigning people. That is the part Plainova takes off your hands — not the responsibility for it.
Existing, unsorted tasks — or simply a list of titles, the way it came out of the meeting.
Placement into phases, dependencies, effort estimates, required skills and concrete assignments — taking your employees’ skills and absences into account.
The proposal arrives as a complete, independent plan version. Your existing plan is left untouched — you compare them in the Gantt chart you already use.
If the draft fits, it goes live. If it does not, you delete it like any other version. Nothing happens that you cannot take back.
Natural-language search translates your question into a real query against your model — not into a fuzzy full-text match.
Describe object types, attributes and relations in a dialogue instead of creating them by hand. Restricted to administrators.
Describe an automation step in one sentence; Plainova compiles it into a configured, reviewable workflow action.
Create and change by instruction — in the context of the object type, with the rules and attributes that apply there.
One principle throughout: no AI result is saved silently. Proposals are shown before they take effect — you accept, adjust or discard them. AI consumption is visible at any time.
The approach behind it — why Plainova is more than a language model
Solutions
Every solution runs on the same data model — and can be cut to your own terms instead of forcing you into someone else’s. Each one has its own page with the details.
Phases, tasks and subtasks with a Gantt chart and dependencies. Assignments to employees and an hour model of estimated, planned and booked — so it becomes visible where plan and reality drift apart.
Time series from your own object data, forecast with nine methods — from naive and Holt-Winters through to Prophet. With backtesting, so you know which method to trust on your data.
Capacity, utilisation and conflicts across projects — who is booked how heavily and when, and where overbooking arises.
Process steps, sequences and cycle times — for operations that cannot sensibly be modelled as a project with an end date.
The platform
Planning is the part you see first. Underneath it is a complete platform — your own data model, search, documents, automation and an API — which is why the plan is not an island.
Object types, typed attributes, relations and statuses — defined by you, versioned, so existing records keep the shape they were created with when the model moves on.
Grid, rows or tiles per type, with the columns you choose and an edit dialog whose tabs and groups you lay out yourself.
Fuzzy full-text across every type, plus a question in plain language turned into a real query against your live schema — not a keyword guess. Saved searches re-run against current data.
Folders group anything with anything, regardless of type. Boards turn a status dimension into columns and only allow the transitions your model permits.
Tenders, concepts and briefs in folders you define. The assistant reads PDF and Word and turns what a document says — not what it is called — into planning tasks.
React to a record being created, changed or moved through a status: set a value, add a tag, create a relation, send mail, or hand the record to the language model with an instruction.
Nine methods on your own time series, backtested against history they were not shown, with MAE, RMSE and MAPE per run so the comparison is measured rather than argued.
Phases, tasks, dependencies, skills and absences, with a solver that produces a schedule respecting all of them at once — and produces the same schedule from the same input, every time.
Everything the interface can do, the API can do. CSV import with a preview that shows what would be created before anything is.
Data model
Most planning tools decide up front what your world looks like: project, task, resource. Plainova does not. At its core sits a generic meta-model made of three building blocks:
A new field, a new object type, a new link: all configured at runtime. No schema migration project, no waiting for the next release — and if your most important entity is called neither “project” nor “ticket”, that is not a special case here, it is the normal one.
Pricing
Prices per user and month, excl. VAT. The free plan stays free — including after the three months.
€0
To try it out, and for small models.
Most chosen
€9.90/ user / month
For teams that work with it, not just test it.
€49/ user / month
When AI spend needs to be predictable.
On AI usage: Plainova uses language models for natural-language search, AI-assisted editing, plan proposals and workflow steps. On the free plan you supply your own provider key; on Team and Company it runs through us.
For developers
Plainova is API-first: the web interface uses the same REST API that is open to you. No reduced “integration API” bolted on as an afterthought.
# Sign in and take the token
curl -s -X POST https://your-tenant.plainova.com/api/auth/login \
-H "Content-Type: application/json" \
-d '{"email":"...","password":"..."}'
# Read objects
curl -s https://your-tenant.plainova.com/api/objects \
-H "Authorization: Bearer $TOKEN"
Operations
Plainova is delivered as a service. There is nothing to install and nothing to patch: you open a browser, and the version you see is the current one.
It runs on AWS in Frankfurt. Your data does not leave the EU region, and each customer gets their own subdomain and their own separated data — not a shared table with a filter over it.
Before you ask
Yours. Object types, attributes, relations and statuses are defined per installation, and there is no industry hard-wired into the product. That is the reason the same system plans film productions and product launches.
On AWS in Frankfurt, in the EU region, and it stays there. Databases have no public address; documents live in versioned object storage that can only be reached through signed links that expire.
Nothing. Plainova runs in the browser, under your own subdomain. Updates are ours to deploy; there is no client to roll out.
Yes, and without asking us. The export on the data page and the REST API both reach everything the interface can. Getting your data out is not a feature we hold back.
No. Without an API key configured, the AI features stay off and the rest of the platform works exactly as it does with them. They are a way to skip legwork, not a dependency.
Only what the request needs, and only when you use an AI feature — the object you have open, the document you asked about, the plan you want drafted. The provider and the key are configured per installation, so you know which service that is.
No. Where a single sentence could mean many changes — a plan, a data model — the assistant proposes and you confirm. A plan proposal even arrives as its own version, so your existing plan is untouched until you activate it.
No. The REST API and CSV import exist so Plainova can sit alongside what you have. Most installations start with one area — usually planning — and grow from there.
Something not answered here? Ask us — a short answer is cheaper for both of us than a long demo.
The fastest way to find out is a conversation — with your model, not with a demo database.
info@createctrl.com +49 89 55 27 77-0
Plainova is a product of CreateCtrl AG, Munich.