Home
Everything waiting for you on one page: cost centers to approve, investments to confirm, a colleague's position to take over, notes that ask you something. Below it, every open round with its progress.
v0.0.0
Planners see their actuals and enter their plan in one place. Controllers see where every cost center stands. The approved plan lands next to your warehouse data, ready for reporting. Open source and self-hosted.
Sound familiar?
Then Planlayer is worth a look.
What it is
Planlayer reads master data and actuals from your data warehouse, gives each planner their cost centers to plan, takes the plan through approval, and writes the result back next to your warehouse data.
It is built for companies whose actuals already sit in a warehouse, and whose planning still runs on files sent around by email, collected and loaded by hand.
Features
Planning can get complicated. Planlayer modules guide users through the process and allow for collaborative planning work.
Everything waiting for you on one page: cost centers to approve, investments to confirm, a colleague's position to take over, notes that ask you something. Below it, every open round with its progress.
One cost center, its accounts down the side and the months across, with last year's actuals beside every line. Group totals are computed from the lines.
Type the year and Planlayer fills the months: evenly, by a seasonality profile, or like last year's actuals. Each line can follow its own rule, and the months always add up to what you typed.
Ask a question where the number is. Mention a colleague, assign it as a task, resolve it when it's answered. Open notes carry over into the next round.
The controller decides how each group of accounts is planned and what it is compared against. The preview beside the settings shows the sheet planners will get, updated with every change.
Every cost center's state, rolled up the hierarchy: who has started, who has submitted, what is approved. Approvers act from the same page.
All of a planner's investments in one list, across their cost centers. Large projects are broken into lines with their own dates; investments are confirmed one by one, or several at once.
Planned, confirmed and open amounts by priority, rolled up the cost center hierarchy or by type, with the cash out per period.
Hours per work center and activity type, planned against last year's. Hours times rates become the credits on the productive cost center.
FTE and headcount per staff type and category, from individual positions with entry and leave dates, next to HR's actuals.
Pay per position, kept by HR and handed over to the cost center when it is ready. Salaries, raises, yearly extras and contributions are calculated per month and posted to their accounts.
Before anything is written, see every row a publish adds, changes or removes. Only approved cost centers go out by default, into tables your reports already know how to read.
Who uses it
Set up the round: what is planned, by whom, in what form, and against which comparisons. They follow progress and publish the result.
Cost center owners and their deputies plan their own cost centers, with last year's actuals beside each line.
Review, send back or approve, from the cost center up through the hierarchy.
Keeps salaries and decides who reads them.
How it fits in
source
For each dataset Planlayer needs (cost centers, accounts, hierarchies, actuals), you give it a query or a view and name the columns. Every sync shows what it will change before it writes anything.
planlayer_app
Planlayer keeps its data in a schema of its own, in a Postgres you already run. There is no separate database server to look after.
planlayer_out
Published plans go to a second schema, as documented fact tables and views. Your reports read them like any other table.
01 Planning
A planner opens Planlayer and finds what is waiting for them: their cost centers, the deadline, the notes addressed to them. Each sheet shows one cost center with last year's actuals beside every line, so the plan starts from something real.
Typing a year total is enough. Planlayer spreads it over the months the way the controller set up for that line (evenly, by season, or like last year), and the months always add up to the total. Planners who want to work month by month can. Undo goes back several steps, and if a colleague changed the same cell in the meantime, Planlayer says so instead of overwriting it.
02 Status
Every cost center has a state: not started, in progress, submitted, approved. The status page rolls those states up the hierarchy, so a controller sees at a glance which division is behind, and a department head sees what is waiting for their approval.
Totals are computed from the lines, never stored on the side, so a roll-up always matches what was planned. Comparison columns show prior years and other versions next to the plan. Notes sit on the line they are about, with mentions and tasks, and stay open until someone resolves them. Every change records who made it, when, and what the value was before.
03 Setup
A planning round is a budget, a forecast or a scenario for one fiscal year. The controller decides per account group whether planners type months or a year total, which accounts each cost center sees, and which columns they compare against. A preview beside the settings shows the sheet the planner will get.
The next round starts from the last one: pick what to carry over, optionally with the plan values and an uplift.
Forecasts close the months that are behind you. Those months show actuals and can't be planned; a year total typed in a forecast covers the whole year, and the remainder goes to the open months.
04 Control
Approvers are assigned on the hierarchy, so a department head sees their area and the CFO sees everything. A cost center goes back to its planner with a comment, or forward with an approval.
Locks and rights live in Postgres itself, through row-level security and triggers. A submitted cost center can't be changed by the app, a script, or someone with a SQL console and the app's credentials.
Modules
Modules are switched on per round, so a company uses what it needs.
Plan hours per work center and activity type; hours times rates credit the productive cost center.
Pass service costs on to the cost centers that use them, by shares, a fixed amount, or rate times quantity. Both sides see the result on their sheet, exact to the cent.
Plan FTE and headcount, or individual positions with entry and leave dates. Positions move between cost centers by proposal and acceptance.
Salaries, raises, yearly extras and contributions calculated per position and month. Pay stays with HR and the people HR names.
One list of planned investments across a planner's cost centers, large projects broken into lines, confirmation one by one, and the cash out by period.
Publishing
When the plan is ready, the controller previews what will change in the output: rows added, changed and removed, per cost center. The run writes exactly that, or refuses if something changed in between. By default only approved cost centers are published. The same data can be downloaded as CSV or Parquet.
Scope
Planlayer plans; it doesn't consolidate. There is no FX translation, intercompany elimination, allocation engine or general formula language, and no balance sheet planning.
Open source
Planlayer is licensed under Apache 2.0. It runs as one container against Postgres 18 or newer. A DBA creates two schemas and a role with the install script; Planlayer manages its own tables from there.
The project is in active development, and more features are coming. See the backlog for what is planned, and request a feature by opening an issue on GitHub.
# what an installation needs
postgres ≥ 18
schemas planlayer_app
planlayer_out
container planlayer
license Apache-2.0