Five fabrication workspaces
FDM, Resin, Mold, CNC and Laser share one desktop environment instead of forcing the user to rebuild the same source geometry for every process.
Current desktop build · 94.0.15 · 94g6
Inspect the job. Then commit the material.
GcoWorks is a local-first desktop fabrication environment for preparing and inspecting manufacturing output across FDM, Resin, Mold, CNC and Laser workflows.
One source asset stays authoritative while process-specific generation, simulation, diagnostics and preflight feedback remain visible before material and machine time are committed.
5 fabrication workflows
129/129 current regression PASS
Local-first core workflow
Advanced functional prototype. Software generation, simulation and validation workflows are implemented. Physical machine, material and mold validation remain the next major proof.
System direction
One source. Five manufacturing workflows.
GcoWorks keeps the imported or created asset as the source of truth, then derives only the process data needed for the manufacturing route that actually applies.
Ready / Review / Blocked
A shared preflight model exposes errors, warnings, confidence and output-readiness rather than presenting uncertain output as automatically safe.
Local-first processing
Core preparation, generation, simulation, diagnostics and project output are designed to remain on user-controlled hardware.
Active work-area authority
The user-defined work area is the manufacturing inclusion volume. Source geometry is not silently scaled, centered or modified simply to fit it.
Traceable output
Generated output can be accompanied by logs, timing, metrics, summaries and validation results so decisions remain inspectable.
Shared transform logic
Position, rotation, scale and source provenance remain consistent as applicable geometry moves between manufacturing contexts.
Current desktop scope
Five workspaces. One verification mindset.
Each process keeps its own manufacturing logic, while inspection, transform behavior, work-area rules and visible preflight feedback follow one product direction. Click any screenshot to inspect the current interface at full size.
01 · FDM
Generated layers as real 3D output.
FDM preview represents deposited material as volumetric extrusion beads derived from generated G-code. Build and All views preserve the generated layers rather than skipping them for speed.
Outer / inner wallsSkin / infillAdhesion / supportTravel inspectionAdaptive support reachWork-area clipping
02 · Resin
Layer inspection tied to process data.
Resin supports multi-model slicing and selected-layer inspection with previous/current comparison and layer-linked exposure, lift and retract information.
Multi-model slicingSelected-layer previewPrevious-layer comparisonExposure / lift / retract
03 · Mold
Generated mold geometry stays inspectable.
The current Auto workflow can generate a smooth exactly-two-half mold path for applicable geometry, with smooth registration geometry, measured clearance checks and authoritative generated parts that remain editable in the main scene. Analysis warnings remain visible where real demolding still needs physical proof.
Configurable split directionTwo generated main halvesRegistration pins / socketsClearance fidelity checksAssembled / exploded / cavity viewsGenerated parts transferable to FDM / CNC
04 · CNC
Progressive motion and carved-result inspection.
CNC simulation follows generated motion order and separates rapid travel from feed motion. Carved progress can be inspected without resetting the user’s camera.
Rough / finish foundationsPocket / contour logicProgressive carved resultTravel vs cut distinctionWork-area intersectionSafety limits stay independent
05 · Laser
Process paths remain distinct from travel.
Laser preview keeps rapid G0 moves as travel only while G1 process moves retain Raster, Engrave and Cut meaning. Repeated passes remain visible in real G-code order.
Line / fill workflowsRaster / engrave / cutTravel inspectionRepeated-pass timeline3D-orbitable workplaneSVG-oriented editing foundations
Current software evidence
Working software, with a protected output baseline.
GcoWorks 94.0.15 is a render/viewer-performance release built on 94g5. Manufacturing output generation is intentionally frozen relative to that base.
129/129
Current regression suite
The current regression set passes after the final render-scheduler changes. This is software verification, not a claim of physical manufacturing accuracy.
PASS
Release integrity
- Release-freeze audit
- Backend syntax
- Runtime source guard
- Offline runtime policy
=
Output protection
Bundled sample comparisons between 94g5 and 94g6 produced byte-identical generated output for FDM, CNC and Laser.
Viewer performance
Main and CNC viewers reduce idle cadence while direct interaction remains 60 FPS. Background cadence is further reduced when appropriate.
Mold rendering
The Mold viewer moved away from perpetual idle traversal to event-driven synchronization and rendering.
Resin rendering
Selected-layer updates now target previous/current material state instead of scanning every layer for each change.
What still has to meet physical reality.
The software can inspect, generate, simulate and flag known conditions. It does not replace machine-specific setup, operator judgement or real material testing.
Next proof
- Run controlled real fabrication jobs across FDM, Resin, CNC and Laser.
- Print, assemble, cast or press representative Mold output.
- Measure dimensional error, failed jobs, time, material use and rework.
- Compare digital warnings and predictions with the physical result.
Known boundaries
- Difficult FDM support cases still require continued physical and geometry validation.
- Complex molds may still expose genuine undercut or demolding constraints.
- Fit, leakage, release, clamping and physical demolding are not yet validated as manufacturing claims.
- Hardware-specific safety limits must come from verified real values, not generic defaults.
Browser STL preview demo
This public browser demo is a lightweight local STL preview of the shared GcoWorks interface shell. It intentionally exposes only the 3D / CNC / Laser preview controls shown here; Resin and Mold capabilities belong to the desktop prototype and are not simulated in this browser demo. Selected STL files are previewed locally in the browser and are not uploaded to our own servers.
GcoWorks
GcoWorks Privacy Policy
Effective date: August 31, 2026
Last updated: August 31, 2026
Platform status: GcoWorks is a local-first fabrication application in active development. The current desktop prototype includes FDM / 3D printing, CNC, Laser, Resin and Mold workspaces. iOS and Android versions may be distributed in the future. Before any public mobile release, this policy and the relevant App Store / Google Play privacy disclosures will be checked against the exact permissions, SDKs and services used by those final builds.
Scope
This policy covers the GcoWorks desktop prototype, any future iOS or Android versions released under the GcoWorks name, and the public GcoWorks project page and browser STL preview demo.
Core Local-First Processing
GcoWorks is designed so that core model inspection, fabrication preparation, validation, diagnostics, previews and project outputs can remain on user-controlled hardware. An account is not required for the current core local workflow. GcoWorks does not require continuous upload of project files to a developer-operated cloud service for core local processing.
Files and Fabrication Data
Depending on the workflow, GcoWorks may process user-selected 3D models, STL, OBJ, GLTF/GLB, SVG, DXF, images, CNC relief inputs, Laser design files, Resin layer/export data, Mold data, generated G-code, generated Mold STL parts, manifests, screenshots, logs, metrics, summaries, validation results, machine-readiness information and fabrication reports. These materials are intended to remain on user-controlled storage unless the user intentionally exports, shares, copies, backs up or sends them through another service.
iOS and Android Permissions
A future mobile build may request only the operating-system permissions needed by the feature the user chooses to use. This may include access to user-selected documents or media for importing fabrication files, local storage for saving exports, and local-network access if a future feature communicates with compatible devices or machines on the user’s network. Notification permission may be requested if a released mobile feature provides local job or process alerts. GcoWorks does not need access to a user’s full Apple or Google account credentials. The exact permission set will be finalised and disclosed before public mobile release.
Diagnostics and Logs
GcoWorks may create local diagnostic logs, generation timing information, validation results, Ready / Review / Blocked preflight summaries, machine-readiness reports, motion metrics, support reports, simulation information, quality summaries and technical reports. These materials are intended for local troubleshooting and review unless the user chooses to share them. If a future public build offers optional crash reporting or analytics, the exact data and provider will be disclosed before release and reflected in the relevant store privacy disclosures.
Public Browser STL Preview Demo
The browser demo is a lightweight local STL preview and intentionally exposes only the 3D / CNC / Laser preview controls shown on this page. Resin and Mold capabilities belong to the desktop prototype and are not simulated in the browser demo. Selected STL files are read locally by the browser for preview and are not designed to be uploaded to our own servers by the demo.
The browser demo currently loads viewer modules from the unpkg content-delivery network. As with ordinary web requests, that provider may receive technical request information such as IP address, browser/device information and request timing. This does not change the intended local handling of the STL file selected for preview.
Apple, Google and Distribution Services
If GcoWorks is distributed through Apple App Store or Google Play, those platforms may independently process information associated with downloads, purchases, subscriptions, device operation, diagnostics, crash reporting or store accounts under their own privacy policies. Where a platform provides an in-app purchase or payment system, payment processing is handled by that platform; GcoWorks does not receive or store full payment-card details.
Third-Party Hardware, Networks and Services
If a user chooses to connect third-party fabrication hardware, storage, a network device, file provider or another external service, that external system may process data according to its own terms and privacy policy. GcoWorks cannot control the data practices of hardware, networks or services selected by the user.
Data Sharing and Sale
GcoWorks does not sell user fabrication files, locally generated project outputs or local fabrication settings. Core local project files are not designed to be uploaded to our own servers unless the user intentionally uses a future feature that clearly requires upload, synchronization, collaboration or cloud processing. Any such feature will be disclosed before release.
Advertising and Tracking
The current GcoWorks prototype is not designed around advertising identifiers or cross-app advertising tracking. If a future mobile release changes this, the policy, consent flow and App Store / Google Play disclosures will be updated before that release.
Retention and Deletion
Files and outputs stored locally remain on user-controlled storage until the user removes them through GcoWorks, the operating system or the relevant storage location. Because local-only files are not designed to live in a developer-operated GcoWorks account service, remote recovery or remote deletion may not be possible for local-only content.
Security and Prototype Status
Local-first processing reduces the need to transmit fabrication files to an external service, but no software, device or network can be guaranteed to be completely secure. GcoWorks remains under active development and physical manufacturing validation is still required. Software preflight output should not be treated as a substitute for machine-specific safety procedures, operator judgement, manufacturer instructions or physical verification.
Children’s Privacy
GcoWorks is not designed specifically for children. It is intended for general fabrication preparation, model inspection, diagnostics, validation and machine-oriented workflows. Where a school, lab or supervised environment uses GcoWorks, the responsible organisation remains responsible for its own consent, supervision and device-management requirements.
Changes to This Privacy Policy
This policy may be updated when GcoWorks architecture, mobile permissions, connected services, distribution method or data-handling practices change. The current version will be posted on this page with a revised date.
Contact
For privacy questions or project enquiries, contact creatooo.com@gmail.com.