Skip to content
@specklesystems

Speckle

The collaborative data hub that connects with your AEC tools

Speckle


Speckle - Your AEC Data Hub

Twitter Follow Community forum users website docs

Speckle is the first AEC data hub that connects with your favorite AEC tools. Speckle exists to overcome the challenges of working in a fragmented industry where communication, creative workflows, and the exchange of data are often hindered by siloed software and processes. It is here to make the industry better.

Features

  • Object-based: say goodbye to files! Speckle is the first object based platform for the AEC industry
  • Version control: Speckle is the Git & Hub for geometry and BIM data
  • Collaboration: share your designs collaborate with others
  • 3D Viewer: see your CAD and BIM models online, share and embed them anywhere
  • Data Connectivity: get your CAD and BIM models into other software without exporting or importing
  • Real time: get real time updates and notifications and changes
  • Automate: full on CI/CD pipelines on top of your Speckle data, the first of its kind in AEC
  • GraphQL API: get what you need anywhere you want it
  • Webhooks: the base for a automation and next-gen pipelines
  • Workspaces: built for teams and designed to make you more productive as a group while benefiting from higher security, better permission management, and stronger collaboration
  • Built for developers: we are building Speckle with developers in mind and got tools for every stack
  • Built for the AEC industry: Speckle connectors are plugins for the most common software used in the industry such as Revit, Rhino, Grasshopper, AutoCAD, Civil 3D, Excel, Unreal Engine, Unity, QGIS, Blender, ArchiCAD and more!

Components

Principles & SDKs

Speckle is not a file based system - it's a versioned object graph storage for large 3D models, with multiple persistance layers. Read more about the core architecture here. What this means, in short, is that we decompose 3D data into their subconstituent atomic parts, hash them and store them in various places, such as databases, the Speckle Server, or the file system. We allow you to access this data in a linear fashion, suited for various processing tasks, or in a structured manner, suited for authoring applications and human understanding.

Connectors

We take data out of design applications via a set of tightly integrated connectors that talk with the native APIs of the host application. Here are some of our connectors, at a glance:

The Speckle Server

Our primary storage layer is the Speckle Server - where Speckle's object decomposition is backed by access control, a querying api, a snazzy frontend and online 3D viewer, and more. Here are some of the components, at a glance:

  • Speckle Server: the Server, a nodejs app. Core external dependencies are a Redis and Postgresql db.
  • Speckle Frontend: the Frontend, a static Vue app.
  • 3D Viewer: a threejs extension that allows you to display 3D data
  • and more!

Community & Contributions

At Speckle, our mission is to make the AEC industry better. This starts by building a tightly connected team that shares thoughts and data openly. This is our approach, and we want you to achieve the same. Join our Community Forum and be part of the journey!)

Pinned Loading

  1. speckle-server speckle-server Public

    The Speckle Server, Frontend, 3D Viewer, & other JS utilities.

    TypeScript 675 175

  2. speckle-sharp-connectors speckle-sharp-connectors Public

    Speckle Connectors V3

    C# 16 5

Repositories

Showing 10 of 103 repositories
  • speckle-sharp-connectors Public

    Speckle Connectors V3

    specklesystems/speckle-sharp-connectors’s past year of commit activity
    C# 16 Apache-2.0 5 0 9 Updated Nov 15, 2024
  • speckle-cpp-connectors Public

    Archicad and possibly other connectors

    specklesystems/speckle-cpp-connectors’s past year of commit activity
    C++ 3 0 1 0 Updated Nov 14, 2024
  • speckle-server Public

    The Speckle Server, Frontend, 3D Viewer, & other JS utilities.

    specklesystems/speckle-server’s past year of commit activity
    TypeScript 675 175 66 35 Updated Nov 14, 2024
  • helm Public
    specklesystems/helm’s past year of commit activity
    Smarty 4 2 0 1 Updated Nov 14, 2024
  • speckle-sharp-sdk Public

    The Speckle SDK/Core for V3

    specklesystems/speckle-sharp-sdk’s past year of commit activity
    C# 13 Apache-2.0 1 0 4 Updated Nov 14, 2024
  • engine_web-ifc Public Forked from ThatOpen/engine_web-ifc

    Reading and writing IFC files with Javascript, at native speeds.

    specklesystems/engine_web-ifc’s past year of commit activity
    TypeScript 0 MPL-2.0 198 0 1 Updated Nov 14, 2024
  • pygeoapi Public Forked from geopython/pygeoapi

    pygeoapi is a Python server implementation of the OGC API suite of standards. The project emerged as part of the next generation OGC API efforts in 2018 and provides the capability for organizations to deploy a RESTful OGC API endpoint using OpenAPI, GeoJSON, and HTML. pygeoapi is open source and released under an MIT license.

    specklesystems/pygeoapi’s past year of commit activity
    Python 0 MIT 267 0 0 Updated Nov 14, 2024
  • specklesystems/speckleCon2024_GIS_workshop’s past year of commit activity
    HTML 0 Apache-2.0 0 0 0 Updated Nov 14, 2024
  • specklesystems/SpeckleConWorkshop-QAQC’s past year of commit activity
    Python 1 Apache-2.0 0 1 0 Updated Nov 14, 2024
  • interactive-insights Public

    Interactive Insights Workshop

    specklesystems/interactive-insights’s past year of commit activity
    TypeScript 2 0 0 0 Updated Nov 14, 2024