Skip to content
@neurocad-eu

NeuroCAD

Implicit geometry for physical design and engineering.

NeuroCAD

Implicit geometry for physical design and engineering.

NeuroCAD is building a production-oriented engineering stack across implicit geometry, solver-ready data generation, model training workflows, and enterprise integration surfaces.

This GitHub organization is the public technical layer around that system.

It exists to expose the parts of NeuroCAD that should be inspectable by partners, customers, and the engineering community: API contracts, benchmarks, examples, and shared technical documentation.

What exists today

NeuroCAD already operates across four technical layers:

  • implicit geometry infrastructure for physical design workflows
  • simulation-grade data generation pipelines
  • model training and evaluation workflows
  • enterprise-facing integration surfaces

The public repositories in this organization are intended to show real technical structure and real engineering output without disclosing proprietary implementation details.

Public surface

Current public repositories:

Operational signals

The public layer is intentionally structured to show engineering discipline:

  • versioned GitHub releases across the public repositories
  • validation workflows on contracts, examples, benchmark packages, and architecture docs
  • explicit public schemas and sample artifacts
  • release notes and checksums for benchmark packaging
  • architecture decision records for public boundary choices

This is not a marketing mirror. It is the inspectable technical shell around the private platform.

Public docs entry point

The primary public documentation landing page for integrations is:

Private core

The following layers remain proprietary:

  • production kernel internals
  • large-scale training infrastructure
  • internal data generation pipelines
  • deployment and operational systems

This is a deliberate boundary. We believe a serious engineering company should expose a clear technical surface to the world while protecting the implementation details that define its core IP.

For partners and technical diligence

NeuroCAD is built for industrial and enterprise contexts where geometry, simulation, data pipelines, and system integration have to be credible, reproducible, and operationally disciplined.

If you are evaluating NeuroCAD for:

  • enterprise integration
  • technical partnership
  • research collaboration
  • infrastructure or model diligence

please contact us directly.

Working with the public repositories

  • use GitHub issues for repository-scoped documentation or integration questions
  • use private email for security disclosure and diligence paths
  • expect the public surface to evolve through tagged releases rather than silent changes

Links

Pinned Loading

  1. neurocad-architecture neurocad-architecture Public

    Public system architecture, trust boundaries, ADRs, and diligence-facing documentation for NeuroCAD.

  2. neurocad-examples neurocad-examples Public

    Reference clients, webhook receivers, and sandbox smoke tests for NeuroCAD integrations.

    Python

  3. neurocad-api-docs neurocad-api-docs Public

    Versioned public API contracts, schemas, integration guides, and SDK references for NeuroCAD.

    Python

  4. neurocad-benchmarks neurocad-benchmarks Public

    Versioned public benchmark releases, sample-set metadata, and evaluation methodology for NeuroCAD.

    Python

  5. .github .github Public

    Organization profile and default community health files for NeuroCAD.

Repositories

Showing 5 of 5 repositories

People

This organization has no public members. You must be a member to see who’s a part of this organization.

Top languages

Loading…

Most used topics

Loading…