Card control logic
Review how limits, freezes, merchant rules, and spend policies are modeled in code.
Spend less.
Control more.
Open-source spend control infrastructure with approvals, policy rules, live visibility, and accounting sync you can inspect and adapt.
Open-source workspace
Inspectable workflows
Open-source product suite
Inspect and adapt the platform
Cards, approvals, and accounting workflows in one codebase - built for teams that want control without a closed platform.
View source
Receipt workflow
Capture receipt context close to the transaction and keep records easy to audit.
Approval engine
Customize request routing and reviewer logic without waiting on vendor roadmaps.
Policy rules
Adapt spend rules for your organization and keep the decision trail transparent.
Accounting sync
Map, categorize, reconcile, and sync transaction data through transparent workflows.
Roles and access
Manage users, permissions, and review ownership from an inspectable admin layer.
Transparent ledger
Keep spend data readable, portable, and ready for downstream reporting.
Reimbursements
Review requests, approvals, and payout state in a workflow you can extend.
Open source beats black-box spend tools
Parowin is built for teams that want transparent spend workflows, direct control over policy logic, and the ability to self-host or extend the system.
Closed platform
Parowin OSS
Source access
Closed product, limited visibility
Inspect the workflows and adapt them to your stack
Customization
Wait for vendor roadmap decisions
Change policy, approvals, and sync logic directly
Deployment
Hosted only, with fixed product boundaries
Run it locally, self-host, or use it as a reference implementation
Data ownership
Exports and reports live behind vendor controls
Keep spend data portable and readable from the start
Approval logic
Generic rules that rarely fit every workflow
Transparent routing and review states you can modify
Accounting sync
Black-box mappings and hard-to-debug exports
Trace categorization, reconciliation, and ERP sync end to end
Community roadmap
Built around sales priorities
Open issues, pull requests, and public iteration
Implementation cost
Paid plan before you can fully evaluate
Clone, inspect, and prototype before committing
Extensibility
Integrations depend on vendor support
Extend the codebase for your accounting and operations stack
Source access
Closed platform
Closed product, limited visibility
Parowin OSS
Inspect the workflows and adapt them to your stack
Customization
Closed platform
Wait for vendor roadmap decisions
Parowin OSS
Change policy, approvals, and sync logic directly
Deployment
Closed platform
Hosted only, with fixed product boundaries
Parowin OSS
Run it locally, self-host, or use it as a reference implementation
Data ownership
Closed platform
Exports and reports live behind vendor controls
Parowin OSS
Keep spend data portable and readable from the start
Approval logic
Closed platform
Generic rules that rarely fit every workflow
Parowin OSS
Transparent routing and review states you can modify
Accounting sync
Closed platform
Black-box mappings and hard-to-debug exports
Parowin OSS
Trace categorization, reconciliation, and ERP sync end to end
Community roadmap
Closed platform
Built around sales priorities
Parowin OSS
Open issues, pull requests, and public iteration
Implementation cost
Closed platform
Paid plan before you can fully evaluate
Parowin OSS
Clone, inspect, and prototype before committing
Extensibility
Closed platform
Integrations depend on vendor support
Parowin OSS
Extend the codebase for your accounting and operations stack
Open integrations
Connect the stack you already use.
Use Parowin as an open integration layer for categorization, mapping, and accounting sync without hiding the workflow behind a vendor black box.
Today
Apr 14
b
Blue Bottle
$11.83
u
Uber
$31.19
CategorizedTravel & transit
sg
Sweetgreen
$27.50
Mapped fields
ERPMerchantUber
CategoryTravel & transit
GL code6200 - Travel
ok
Synced
Uber ride is in your accounting system.
Synced
Open source
git clone https://github.com/neelmanro/parowin
cd parowin
npm install
npm run devFork it. Run it. Make it yours.
Parowin is now positioned around open-source adoption: inspect the code, prototype locally, and adapt the workflows to your own operating model.
- Public repository first
- Self-host and customize
- Open issues and contributions
Developer path
From clone to custom workflow
Start with the open repository, then shape approvals, policy, and accounting sync around the way your organization actually works.
From source to deployment
01Clone
Clone the repository
Pull the source locally and inspect the app structure before changing anything.
02Configure
Configure your workflow
Adapt roles, approval paths, policy rules, and environment settings for your setup.
03Integrate
Connect your systems
Wire accounting, data, and notification services into the open workflow layer.
04Deploy
Run it your way
Self-host, contribute improvements, or use Parowin as the base for your internal spend tooling.
No onboarding call required. Start with the code and evaluate the system on your own timeline.
Built for real workflows, not a black box.
Keep the product experience polished while keeping the underlying logic open, inspectable, and ready to extend.
Trust & transparency
Open workflows are easier to trust
Fraud & Risk Protection
Keep transaction monitoring, spend rules, and risk checks visible so teams can reason about how decisions are made.
Audit Trail
OpenReview approvals, exceptions, and accounting changes through a workflow designed for traceability.
Infrastructure
Self-hostable
Bring your own controls
Run Parowin in the environment you trust, connect the services you choose, and keep security reviews grounded in source code.
Project notes
Notes on open spend infrastructure
Practical notes on policy logic, accounting sync, and building transparent financial workflows.
Why spend workflows should be inspectable
Open source makes approval logic, policy checks, and accounting sync easier to reason about.
Read note
Designing policy rules that teams can change
Policy logic should be explicit, portable, and easy to adapt as workflows change.
Read note
Making reimbursement workflows extensible
Requests, approvals, payout state, and audit history should be easy to model and extend.
Read note
Accounting sync should be debuggable
Mapping and reconciliation are easier to trust when the sync path is visible.
Read noteFAQ
Open-source questions
Straight answers on source access, self-hosting, integrations, and contribution.
Is Parowin open source?
Yes. The landing page now presents Parowin as an open-source project you can inspect, fork, and adapt.
Can we self-host it?
The project is positioned for teams that want to run and customize the code themselves. Check the repository for the current setup instructions and deployment notes.
What can we customize?
Approval routing, policy rules, accounting sync, roles, and workflow states are presented as parts of the system you can inspect and adapt.
Does it still support accounting integrations?
The product direction still centers on mapping, categorization, reconciliation, and accounting sync, but now the integration story is open and extensible.
Is this a hosted SaaS?
No. The page now points people to the repository first instead of pushing a demo or onboarding conversation.
Can contributors help?
Yes. The open-source positioning encourages issues, pull requests, and community-driven improvements.
Is there a hosted plan?
This page focuses on cloning, evaluating, and running the open-source project.
Where should we start?
Start on GitHub. Clone the repository, run it locally, and review the workflows before deciding how far to customize it.