Less Admin.
More Building
A lightweight operational layer for modern, distributed teams.
Run invoicing, payouts, reporting, and compliance through a single entity
without ops becoming a second job.
Your Operational Hub
Swiss Association • Active
Less Admin.
More Building
A lightweight operational layer for modern, distributed teams.
Run invoicing, payouts, reporting, and compliance through a single entity
without ops becoming a second job.
Your Operational Hub
Swiss Association • Active
Less Admin.
More Building
A lightweight operational layer for modern, distributed teams.
Run invoicing, payouts, reporting, and compliance through a single entity
without ops becoming a second job.
Your Operational Hub
Swiss Association • Active
Who This Is For
Built for teams with $250k+ in annual operating spend who need a repeatable way to run invoicing, payouts, and reporting without building a full back office.
DevCo and builder teams
Teams paying contributors and vendors on a recurring cadence who want operations handled without adding full-time admin headcount.
Open-source builders
Teams maintaining open-source projects who want to own their entity and run a repeatable back office for invoicing, approvals, payouts, and reporting, even when funding comes from many different sources.
Privacy-first teams
Teams that want to run real-world operations with member privacy by default and less personal exposure for signers and operators.
Who This Is For
Built for teams with $250k+ in annual operating spend who need a repeatable way to run invoicing, payouts, and reporting without building a full back office.
DevCo and builder teams
Teams paying contributors and vendors on a recurring cadence who want operations handled without adding full-time admin headcount.
Open-source builders
Teams maintaining open-source projects who want to own their entity and run a repeatable back office for invoicing, approvals, payouts, and reporting, even when funding comes from many different sources.
Privacy-first teams
Teams that want to run real-world operations with member privacy by default and less personal exposure for signers and operators.
Who This Is For
Built for teams with $250k+ in annual operating spend who need a repeatable way to run invoicing, payouts, and reporting without building a full back office.
DevCo and builder teams
Teams paying contributors and vendors on a recurring cadence who want operations handled without adding full-time admin headcount.
Open-source builders
Teams maintaining open-source projects who want to own their entity and run a repeatable back office for invoicing, approvals, payouts, and reporting, even when funding comes from many different sources.
Privacy-first teams
Teams that want to run real-world operations with member privacy by default and less personal exposure for signers and operators.
Why Teams Choose An Operational Hub
Spend less time on operations
Replace admin chaos with workflows
Track payouts, records, approvals
Free contributors to ship
Standardized templates
Start from a proven agreement stack
Fewer drafting and review cycles
Counsel time on specifics, not basics
Payments and compliance
Pay vendors in fiat or stablecoins
Clean invoicing and approval flows
Reporting that scales with you
Privacy and personal protection
Members are not doxxed by default
Legal shield between you and ops
Reduce exposure to the real-world
Legal wrapper for your multisig
Put a legal entity behind your treasury
Sign agreements and pay vendors
Credibly offchain with onchain control
Flexible structure, no lock-in
Start lightweight and evolve
Add structure as you grow
Wind down if needs change
Why Teams Choose An Operational Hub
Spend less time on operations
Replace admin chaos with workflows
Track payouts, records, approvals
Free contributors to ship
Standardized templates
Start from a proven agreement stack
Fewer drafting and review cycles
Counsel time on specifics, not basics
Payments and compliance
Pay vendors in fiat or stablecoins
Clean invoicing and approval flows
Reporting that scales with you
Privacy and personal protection
Members are not doxxed by default
Legal shield between you and ops
Reduce exposure to the real-world
Legal wrapper for your multisig
Put a legal entity behind your treasury
Sign agreements and pay vendors
Credibly offchain with onchain control
Flexible structure, no lock-in
Start lightweight and evolve
Add structure as you grow
Wind down if needs change
Why Teams Choose An Operational Hub
Spend less time on operations
Replace admin chaos with workflows
Track payouts, records, approvals
Free contributors to ship
Standardized templates
Start from a proven agreement stack
Fewer drafting and review cycles
Counsel time on specifics, not basics
Payments and compliance
Pay vendors in fiat or stablecoins
Clean invoicing and approval flows
Reporting that scales with you
Privacy and personal protection
Members are not doxxed by default
Legal shield between you and ops
Reduce exposure to the real-world
Legal wrapper for your multisig
Put a legal entity behind your treasury
Sign agreements and pay vendors
Credibly offchain with onchain control
Flexible structure, no lock-in
Start lightweight and evolve
Add structure as you grow
Wind down if needs change
How it Works
Legal setup comes first. Operational setup follows. Then you run day to day through the entity.
1
Legal Setup
Create your Operational Hub and assemble your contracts with templates for Articles/Bylaws, MPA, governance minutes, contributor agreements and membership records. If required, local Counsel reviews and customizes templates.
External Swiss counsel reviews and customizes templates (not legal advice).
2
Operational Setup
Operator team sets up admin workflows: payouts, vendors, approvals, reporting. Connect the operational pieces you need to run cleanly.
3
Operate
Run payments and agreements through the entity, not as individuals. The operator team handles day-to-day operations and maintains clean documentation for reporting, audits when needed, and tax filings.
What’s included in operator support (typical scope)
Setup and coordination: end-to-end launch, vendor coordination, timeline and checklist ownership
Payments operations: invoicing intake, approvals workflow, payouts scheduling, multi-currency support
Accounting and reporting: bookkeeping coordination, monthly close support, financial reporting package
Tax and filings readiness: tax-ready records, VAT support where applicable, documentation for tax filings
Contracts and workforce ops: contractor and employment agreement templates, classification support with Swiss specialists
Tools and systems: accounting system setup (for example Xero), records storage, repeatable workflows
How it Works
Legal setup comes first. Operational setup follows. Then you run day to day through the entity.
1
Legal Setup
Create your Operational Hub and assemble your contracts with templates for Articles/Bylaws, MPA, governance minutes, contributor agreements and membership records. If required, local Counsel reviews and customizes templates.
External Swiss counsel reviews and customizes templates (not legal advice).
2
Operational Setup
Operator team sets up admin workflows: payouts, vendors, approvals, reporting. Connect the operational pieces you need to run cleanly.
3
Operate
Run payments and agreements through the entity, not as individuals. The operator team handles day-to-day operations and maintains clean documentation for reporting, audits when needed, and tax filings.
What’s included in operator support (typical scope)
Setup and coordination: end-to-end launch, vendor coordination, timeline and checklist ownership
Payments operations: invoicing intake, approvals workflow, payouts scheduling, multi-currency support
Accounting and reporting: bookkeeping coordination, monthly close support, financial reporting package
Tax and filings readiness: tax-ready records, VAT support where applicable, documentation for tax filings
Contracts and workforce ops: contractor and employment agreement templates, classification support with Swiss specialists
Tools and systems: accounting system setup (for example Xero), records storage, repeatable workflows
How it Works
Legal setup comes first. Operational setup follows. Then you run day to day through the entity.
1
Legal Setup
Create your Operational Hub and assemble your contracts with templates for Articles/Bylaws, MPA, governance minutes, contributor agreements and membership records. If required, local Counsel reviews and customizes templates.
External Swiss counsel reviews and customizes templates (not legal advice).
2
Operational Setup
Operator team sets up admin workflows: payouts, vendors, approvals, reporting. Connect the operational pieces you need to run cleanly.
3
Operate
Run payments and agreements through the entity, not as individuals. The operator team handles day-to-day operations and maintains clean documentation for reporting, audits when needed, and tax filings.
What’s included in operator support (typical scope)
Setup and coordination: end-to-end launch, vendor coordination, timeline and checklist ownership
Payments operations: invoicing intake, approvals workflow, payouts scheduling, multi-currency support
Accounting and reporting: bookkeeping coordination, monthly close support, financial reporting package
Tax and filings readiness: tax-ready records, VAT support where applicable, documentation for tax filings
Contracts and workforce ops: contractor and employment agreement templates, classification support with Swiss specialists
Tools and systems: accounting system setup (for example Xero), records storage, repeatable workflows
What You Get
A complete operating bundle, including workflow software and an operator team to run the day to day, plus an entity that can sign, pay and keep records.
Operator Support
An operator team runs recurring workflows for you, so invoicing, approvals, payouts, and close do not become a constant distraction.
Workflow System
Repeatable workflows for invoices, approvals, payouts, and records so operations are consistent month to month, with documentation organized for reporting and tax filings.
Payment Layer
Payouts in fiat or stablecoins with clean approval and recordkeeping, designed for contributor heavy teams.
Agreement Stack
A proven set of templates and agreements that reduces legal costs and gets you to a working setup faster.
What You Get
A complete operating bundle, including workflow software and an operator team to run the day to day, plus an entity that can sign, pay and keep records.
Operator Support
An operator team runs recurring workflows for you, so invoicing, approvals, payouts, and close do not become a constant distraction.
Workflow System
Repeatable workflows for invoices, approvals, payouts, and records so operations are consistent month to month, with documentation organized for reporting and tax filings.
Payment Layer
Payouts in fiat or stablecoins with clean approval and recordkeeping, designed for contributor heavy teams.
Agreement Stack
A proven set of templates and agreements that reduces legal costs and gets you to a working setup faster.
What You Get
A complete operating bundle, including workflow software and an operator team to run the day to day, plus an entity that can sign, pay and keep records.
Operator Support
An operator team runs recurring workflows for you, so invoicing, approvals, payouts, and close do not become a constant distraction.
Workflow System
Repeatable workflows for invoices, approvals, payouts, and records so operations are consistent month to month, with documentation organized for reporting and tax filings.
Payment Layer
Payouts in fiat or stablecoins with clean approval and recordkeeping, designed for contributor heavy teams.
Agreement Stack
A proven set of templates and agreements that reduces legal costs and gets you to a working setup faster.
Frequently Asked Questions
Everything you need to know.
What is an Operational Hub?
An Operational Hub is a turnkey structure for open-source builders and DAO contributor teams. It bundles a compliant Swiss Association with operational and payment workflows so globally distributed teams can operate professionally without sacrificing privacy or autonomy.
Do members have to be public or doxxed?
Not by default. Swiss Associations are generally not required to be publicly listed in a registry in the standard case, which supports privacy-first operations for distributed contributor teams.
What are the key constraints of a Swiss Association?
Swiss Associations are non-profit entities. That means: commercial activities are typically allowed if secondary and supportive to the main purpose; there are no shares (so you cannot receive external investments or issue security tokens as equity); and you cannot pay dividends or distribute profits (members have no claim on the Association's assets).
Can we wind down the Operational Hub later?
Yes. The structure is intended to be flexible: you can start lightweight, evolve as your needs change, and wind down the Hub if it no longer fits your operating model.
How does this protect multisig signers and contributors?
The goal is to separate "you the person" from "you acting on behalf of the organization." When contracts, invoices, and operations are handled through the Association, operational liability is generally shifted away from individuals and onto the entity. However, it does not protect against all risks—managers and multisig signers can still have personal exposure in criminal, regulatory, tax, or employment-law matters, or in cases of willful misconduct or gross negligence.
Why Switzerland and why Zug?
Switzerland is a stable, internationally recognized jurisdiction with mature financial infrastructure. The Hub is based in Canton Zug ("Crypto Valley"), known for crypto-friendly business policies and the presence of many high-profile projects.
What does tax efficiency mean here?
In some cases, a Zug-based structure may pursue a cost plus 5% model via a tax ruling. This is not automatic and depends on your activities. Example: CHF 1,000,000 in annual operating costs → CHF 50,000 taxable income (5% of costs) → at Zug's effective tax rate of ~11%, approximately CHF 5,500 in tax, or ~0.55% of total annual costs. This typically aligns with low-risk service activity (open-source development, consultancy, R&D, admin support) and is usually not suitable for higher risk activity (token sales, active trading, staking/mining, DeFi yield). Requires robust cost accounting and is typically pursued case by case via a tax ruling with Swiss tax advisors. Informational only. Not legal or tax advice.
What does liability protection mean?
Liability is not absolute. The Association structure provides a layer of separation, but managers and signers may still have personal exposure in certain situations including criminal, regulatory, tax, or employment matters, or cases involving willful misconduct or gross negligence.
Frequently Asked Questions
Everything you need to know.
What is an Operational Hub?
Achra lowers the costs of coordination. It connects organizations, builders, and operators in a shared system where governance, payments, and services are integrated. By structuring procurement, automating execution, and aligning incentives, network organizations can grow across borders without the friction of traditional firms.
Do members have to be public or doxxed?
Governance decisions are not left onchain or in the forums. Achra integrates permissions and approvals from governance directly to into workflows, payouts, and records. Atlas powers this layer so that proposals, budgets, and milestones can move from decision to execution automatically.
What are the key constraints of a Swiss Association?
Workstreams are open calls for contribution. Builders submit proposals that describe how they will deliver. Approved proposals roll into roadmaps where progress is tracked and contributors get paid. This creates a structured flow from idea to delivery and keeps the network work structured and transparent.
Can we wind down the Operational Hub later?
Every roadmap, project, and deliverable carries its own wallet. Budgets and expenses are visible at each level, so contributors know how funds are allocated and spent. Milestone-based payouts run in stablecoins, with automated tax reporting to keep compliance manageable.
How does this protect multisig signers and contributors?
Instead of relying on external auditors, Achra introduces operational hubs. Hubs verify that deliverables, budgets, and services line up with governance decisions. They provide a live check on execution, so networks can act with confidence and reduce the lag of periodic audits.
Why Switzerland and why Zug?
Achra’s workflows and data structures are designed for automation from the start. Specifications, approvals, and payouts are machine readable, which makes it possible for AI agents to participate directly in operations. They can draft proposals, monitor execution, and run services in ways that are transparent and safe.
What does tax efficiency mean here?
Powerhouse is the ecosystem for Scalable Network Organizations. It combines services, governance, and software to help decentralized groups grow into platform economies. Achra is Powerhouse’s global coordination platform, where organizations, builders, and operators execute work through RFPs, services, and automated governance. Vetra is the builder platform for creating applications on a reactive document architecture with spec-driven AI, enabling developers to define workflows once and deploy them globally. Together, Achra and Vetra form the operational and technical backbone for SNOs, supported by Powerhouse’s broader framework of services and models. At the core is Open-Source Capitalism, which treats code and models as shared infrastructure, funds development sustainably, and resists the concentration of power in a few centralized platforms.
What does liability protection mean?
Yes. Achra and the Powerhouse stack are released under the Daimon Dual Phase License (DDPL). In its first phase, the license requires contributors who build on the code to share improvements back, protecting early builders from one-sided extraction. After a defined change date, the code automatically converts to a permissive license, ensuring openness for the long term. The DDPL model balances sustainability with accessibility, making open-source development viable while keeping the infrastructure free for everyone over time.
Frequently Asked Questions
Everything you need to know.
What is an Operational Hub?
Achra lowers the costs of coordination. It connects organizations, builders, and operators in a shared system where governance, payments, and services are integrated. By structuring procurement, automating execution, and aligning incentives, network organizations can grow across borders without the friction of traditional firms.
Do members have to be public or doxxed?
Governance decisions are not left onchain or in the forums. Achra integrates permissions and approvals from governance directly to into workflows, payouts, and records. Atlas powers this layer so that proposals, budgets, and milestones can move from decision to execution automatically.
What are the key constraints of a Swiss Association?
Workstreams are open calls for contribution. Builders submit proposals that describe how they will deliver. Approved proposals roll into roadmaps where progress is tracked and contributors get paid. This creates a structured flow from idea to delivery and keeps the network work structured and transparent.
Can we wind down the Operational Hub later?
Every roadmap, project, and deliverable carries its own wallet. Budgets and expenses are visible at each level, so contributors know how funds are allocated and spent. Milestone-based payouts run in stablecoins, with automated tax reporting to keep compliance manageable.
What are the key constraints of a Swiss Association?
A resource is anything a network depends on, such as a builder team, a legal entity, or a treasury. Services attach to these resources in three stages: setup, maintenance, and wind-down. This makes it easy to plug in the right operational support at the right stage of a resource’s lifecycle.
How does this protect multisig signers and contributors?
Instead of relying on external auditors, Achra introduces operational hubs. Hubs verify that deliverables, budgets, and services line up with governance decisions. They provide a live check on execution, so networks can act with confidence and reduce the lag of periodic audits.
Why Switzerland and why Zug?
Achra’s workflows and data structures are designed for automation from the start. Specifications, approvals, and payouts are machine readable, which makes it possible for AI agents to participate directly in operations. They can draft proposals, monitor execution, and run services in ways that are transparent and safe.
What does tax efficiency mean here?
Powerhouse is the ecosystem for Scalable Network Organizations. It combines services, governance, and software to help decentralized groups grow into platform economies. Achra is Powerhouse’s global coordination platform, where organizations, builders, and operators execute work through RFPs, services, and automated governance. Vetra is the builder platform for creating applications on a reactive document architecture with spec-driven AI, enabling developers to define workflows once and deploy them globally. Together, Achra and Vetra form the operational and technical backbone for SNOs, supported by Powerhouse’s broader framework of services and models. At the core is Open-Source Capitalism, which treats code and models as shared infrastructure, funds development sustainably, and resists the concentration of power in a few centralized platforms.