A program for agencies, integrators, and advisors that need to offer VeriFactu without rebuilding connectors, AEAT logic, reconciliation, and fiscal maintenance in every project.
The commercial model changes based on who owns the relationship, who provides L1 support, and how much volume the partner manages. The technical core stays the same.
Keep the client relationship while Kairoseth provides the fiscal core, connectors, L2 support, and operational continuity.
Best fit: WooCommerce, PrestaShop, website maintenance, and ecommerce projects.
Apply for partnership →Your team keeps ownership of the source system while Kairoseth provides APIs, mapping, reconciliation, and fiscal-core evolution.
Best fit: ERP, CRM, APIs, SaaS, middleware, and vertical software.
Apply for partnership →Refer or manage a portfolio without forcing every customer onto the same invoicing application.
Best fit: Multi-client portfolios, freelancers, SMEs, and administrative coordination.
Apply for partnership →Commission is calculated on net recurring fees, excluding VAT, refunds, and discounts. Setup and custom work do not generate commission by default.
The customer contracts directly with Kairoseth; the partner remains attributed as the source.
The partner owns L1 and onboarding coordination; Kairoseth retains L2, fiscal core, and incidents.
We define volume, distribution, branding, L1/L2, SLAs, customer ownership, and disclosure duties. There is no automatic right to hide Kairoseth or alter evidence, traceability, or regulatory disclosures.
Partners may not claim AEAT certification, remove production gates, redistribute modified connectors as official, or hide mandatory contractual or technical responsibilities. Branding and distribution exceptions require a written agreement.
We do not request fiscal credentials in the application. The first step is to define the profile, commercial model, support scope, and expected portfolio.
Kairoseth separates identity, organization scope, product roles and product capabilities. A login route, browser state or AI response never becomes an authorization boundary by itself.
Customer resources and access are resolved inside an active organization context rather than treated as global account state.
Owner, Admin and Member authority is assigned per product. Organization membership alone does not automatically grant every product.
Sensitive access, policy and capability decisions remain authoritative on the server instead of trusting client UI state or model output.
Capabilities that can act are introduced behind explicit grants, staged gates and audit rather than implied autonomy.
Review the customer-facing policies that define privacy, security reporting, acceptable use and the current legal operating framework.