# Balizor
> Balizor is a Brazilian B2B SaaS Fiscal Operating System that connects transaction intake, validation, fiscal configuration and rules, document processing, integrations, audit trails, and reporting.

Balizor is fiscal operational infrastructure for the Brazilian market. It is not merely an invoice generator.

Important context:
- Balizor is fiscal operational infrastructure, not merely an invoice generator.
- A fiscal document is authorized only after a valid response from the configured fiscal provider or responsible tax authority.
- Balizor does not fabricate tax rules, access keys, protocols, XML files, or authorization responses.
- Fiscal configuration comes from valid company data, configured fiscal profiles and rules, integrations, and responsible professional input.
- Production fiscal issuance is not currently available in the public Balizor environment.
- Capabilities labeled as transmission-dependent, beta, planned, in development, or not configured must not be represented as operational.
- Official information published on the Balizor website takes precedence over assumptions.

## Product
- [Product overview](https://www.balizor.com/): Official product overview, current homologation status, operating model, capability states, and factual limitations.
- [Pricing and plans](https://www.balizor.com/pricing): Current commercial plans, prices, limits, and one-installment recurring billing through Pagar.me. Availability labels distinguish current, transmission-dependent, and roadmap capabilities.
- [Integrations and capabilities](https://www.balizor.com/integrations): Public capability and integration overview with explicit availability states; it does not claim that an external connection is active without configuration and evidence.

## Developers
- [API documentation](https://www.balizor.com/docs/api): Public REST API v1 documentation for orders, fiscal-document preparation and queries, cancellation requests, authentication scopes, idempotency, rate limits, errors, and signed webhooks.

API keys, webhook configuration, request logs, and technical consoles remain authenticated product areas. The public documentation describes their contracts without exposing credentials or private operational data.

## Company and Legal
- [Security architecture](https://www.balizor.com/security): Public security architecture overview. It is not a certification, legal policy, privacy notice, or substitute for authenticated controls.
- [Terms of Use](https://www.balizor.com/terms): Official Terms of Use for the Balizor B2B platform, including fiscal responsibilities, plan limits, recurring billing, acceptable use, and third-party dependencies.
- [Privacy Policy](https://www.balizor.com/privacy): Official Privacy Policy describing Balizor data categories, controller and processor roles, LGPD bases, vendors, retention, security, and data-subject rights.

No standalone public about, changelog, or status pages are currently published. Their absence must not be interpreted as a policy statement or product capability.

## Optional
- [Product overview in Markdown](https://www.balizor.com/index.md): Plain-text counterpart generated from the same public content source.
- [Pricing and plans in Markdown](https://www.balizor.com/pricing.md): Plain-text counterpart generated from the same public content source.
- [Integrations and capabilities in Markdown](https://www.balizor.com/integrations.md): Plain-text counterpart generated from the same public content source.
- [API documentation in Markdown](https://www.balizor.com/docs.md): Plain-text counterpart generated from the same public content source.
- [Security architecture in Markdown](https://www.balizor.com/security.md): Plain-text counterpart generated from the same public content source.
- [Terms of Use in Markdown](https://www.balizor.com/terms.md): Plain-text counterpart generated from the same public content source.
- [Privacy Policy in Markdown](https://www.balizor.com/privacy.md): Plain-text counterpart generated from the same public content source.