Specialty
Architecture driven by execution
Product modeling, contracts, quality and operations considered from the first deploy.
Ecosystem
How the lab is organized
MOZG works as a software lab that turns recurring stacks, standards and product needs into reusable assets. The focus is not the number of projects, but the coherence between product, operations, documentation and public distribution.
For case-by-case reading with commands and maintenance notes, also check Projects.
Specialties
Specialty
Full stack engineering
Frontends, backends, authentication, reusable components and high-context experiences.
Specialty
Platform and DevOps
Repeatable environments, health checks, matrix CI, local Docker and safe maintenance paths.
Specialty
Automation and AI ops
Assisted flows, local runtime, guardrails, monitoring and multimodal pipeline integration.
Flagship projects
Multistack workspace
monorepo
Single base for apps, templates, docs, infrastructure, local agents and quality governance.
SaaS platform
node-next
Nx environment with Next apps, cross-app contracts, smoke tests and a Docker-based development stack.
AI ops and automation
python-lumiere-synapse
Local control plane for multimodal pipelines, assisted publishing and safe operations.
Editorial engine
node-vitepress
Institutional and technical site in VitePress with a shared catalog, public exports and an auditable API.
UI library and Storybook
node-web-components
Public Web Components library with Storybook, multiframe wrappers and auditable npm distribution.
Main website
mozg.com.br
Professional positioning, portfolio and editorial layer of the lab on its own domain.
Complementary portal
mozgbrasil.github.io
Public layer with GitHub signals, portfolio and link distribution for channels and projects.
Technical profile
github-profile
Lean summary of specialty, stack and monorepo context for GitHub surfaces.
Monorepo signals
Active stacks
Node.js, Python, Go, Java, PHP, Ruby, Rust, Deno, Bash, Perl, C++ and .NET coexisting with clear scope.
Quality per project
Each subproject closes on its own green pipeline with clearly documented runtime commands.
Infrastructure as product
Docker, Kubernetes, Helm, Terraform, observability and deploy living in the same private workspace.
Auditability
Logs, request metadata, explicit payloads and verification scripts support safer evolution without exposing the source workspace.
Capability matrix
Capabilities
Matrix of domains, technologies and delivery modes.
This slice translates the portfolio into operational capability and makes clear how delivery connects to stack, docs and readiness.
Recurring technologies
Tools that show up consistently across delivery modes.
Domain
Architecture and contracts
Domain modeling, predictable envelopes, auditable routes and structures ready for safe evolution.
Practices- small and clear contracts
- explicit payloads
- low-friction versioning
Domain
Full stack product
Web experiences, reusable components, front and back integrations and operational docs moving together.
Practices- content-driven UI
- searchable flows
- components with simple maintenance
Domain
Platform engineering
Repeatable local environments, matrix CI, infrastructure as product and technical readiness per project.
Practices- local Docker
- validation matrix
- documented runtime standard
Domain
Observability and operations
Health checks, request IDs, static exports, operational snapshots and real verification triggers.
Practices- quality gates
- health endpoints
- public artifacts for auditability
Domain
Automation and AI ops
Local pipelines, assisted automations, execution guardrails and the combination of data, runtime and operations.
Practices- multimodal pipelines
- operational guardrails
- local assistance with context
Delivery mode
Structured diagnosis and refactor
Legacy reading, contract consolidation, architecture cleanup and a green pipeline at the end.
Best suited for- bases with technical drift
- sites and apps without a clear standard
- growing monorepos
Delivery mode
Portfolio and public surfaces
Sites, portals, technical profiles and editorial layers with coherent distribution and strong readability.
Best suited for- technical brand
- public presence
- content with SEO and discoverability
Delivery mode
Auditable minimal API
Small HTTP layers with clear envelopes, filters and data suited for automation and troubleshooting.
Best suited for- lightweight BFFs
- operations with visibility
- future integrations
Delivery mode
Platform readiness
Per-project quality, operational scripts, containerized build and alignment between docs and runtime.
Best suited for- local pipelines
- small teams
- evolution with a strict standard
Public surfaces
Main website
mozg.com.br concentrates positioning, portfolio and the institutional layer of the work.
GitHub Pages portal
mozgbrasil.github.io reinforces public presence with living signals and slices derived from the private workspace.
Developer Play Store
Mozg TWA (Bubblewrap) and Mozg Híbrido (Angular) are active Android products.
Professional profile
github-profile organizes specialties, badges and links to the resume, website and public dossiers of the ecosystem.
Packages and artifacts
History of publishing to npm and Packagist to turn knowledge into reusable modules.