Photonic IC Integrated Design Environment

PIC Different.

Design, simulate, and verify photonic circuits. All in one place.

Try the Alpha Explore Lumicron
Lumicron for Mac showing a Garnet1 photonic circuit schematic and its wavelength-sweep result
Lumicron iPad companion showing a photonic chip layout and device pins

Designed from the ground up for Apple Silicon.

Photonic design should
feel like one discipline.

Photonic engineering moves between tools, files, scripts, and verification results. Too often, the connections are left to you. Lumicron brings the work into one project, so the design record can travel with it.

  1. 01One project.
  2. 02Different ways of working.
  3. 03Shared engineering context.

Big picture.
Fine detail.

Explore your chip, inspect its layers, and take a closer look at each component.

Lumicron Garnet1 layout with a selected spiral and Layout Inspector visible
Layout InspectorIdentity · dimensions · source
Garnet1 Layout Inspector: square_archimedean_spiral, measured portion 165,630 micrometers, width 0.45 micrometers, and layer 3/0, with the rendered-centerline coverage note
Garnet1 Layout Inspector routing context with strip_1550nm and the retained square_spiral.py source location at line 134
Spiral dimensions, routing, and source. Available details depend on the data saved with the layout.
Explore the chip
Browse the hierarchy, choose your layers, and select geometry.
Check the dimensions
Inspect available component and route dimensions, with measured length coverage shown.
See what’s behind it
See component identity, PDK routing, and source links where available.

Find the issue.
Follow the source.

A DRC finding with a source link takes you straight to the relevant line of code.

Lumicron checks that the source still matches. After edits, run DRC again to refresh the link.

Full Garnet1 Layout window showing the taper, its minimum-width violation, and the DRC findings panel.
A minimum-width finding linked to taper.py:18.
See how it connects

Your ideas.
Written in Python.

Create layouts in Python, with project files, packages, Git changes, and run output close at hand.

Garnet1 Script view with square_spiral.py open, the project file tree, and CORNERSTONE package layers in the Inspector
Spiral design in Python, with CORNERSTONE package tools.
Build with Python
Place components and connect named ports with Lumicron’s layout API.
Work with Git
Review source changes right inside your project.
Know your packages
See the versions your project uses. Review updates before applying them.
See Python become a layout

Explore a complete MZI example built with the Elyon Demo PDK.

Complete PCellElyon Demo PDK
@lm.pcell
def MZI(
    span: float = 300,
    imbalance: float = 60,
):
    c = lm.CELL("MZI")
    splitter = c.add(
        pdk.NxM_MMI(n_inputs=1, n_outputs=2))
    combiner = c.add(
        pdk.NxM_MMI(n_inputs=2, n_outputs=1))

    (c.Place(combiner).right_of(splitter)
       .move_by(span, 0))
    c.Route(
        splitter.ports["o2"],
        combiner.ports["i2"],
        profile=pdk.RP.silc_strip)
    (c.Route(
        splitter.ports["o1"],
        combiner.ports["i1"],
        profile=pdk.RP.silc_strip)
       .jog("S", by=imbalance))
    return c
Python designGenerated layout
Lumicron layout viewerNamed ports · PDK route profile
The MZI generated by the Lumicron PCell shown above, open in Lumicron’s layout viewer with named input and output ports
The MZI generated by this code, using the PDK’s routing geometry and layers.

Build a circuit.
Explore the response.

Place components, connect ports, and run circuit simulations. Explore a wavelength sweep right beside your schematic.

Garnet1 MZI schematic with two connected MMI components, Source and Detector, circuit hierarchy, PDK library, and a recorded transmission sweep
Schematic and circuit simulation
Start with your PDK
Place and connect components from your active library.
Plan the layout
Inspect connections and configure physical placement.
See how it behaves
Run supported models, inspect wavelength sweeps, and save experiments to Notebook.

Keep the result.
And the thinking.

Notes, code snapshots, and saved experiments stay with your project. Ready when the next question comes up.

Garnet1 O-Band MZI Notebook showing a completed optical experiment, circuit snapshot, transmission sweep, experiment notes area, and recorded run references
A saved O-Band MZI experiment
Capture the why
Keep notes and design decisions alongside your work.
Save the experiment
Keep circuit snapshots and recorded results together.
Back to the code
Open linked source in Script when you want to dig deeper.

Phoebe

Meet Phoebe.

Your project-aware intelligent photonic design assistant.

Ask Phoebe about your code, PDK, layout, and saved results. She works fully offline, with optional connections to online frontier models or your own custom model.

Hi, I’m Phoebe!How can I help?

Phoebe pixel-art flame mascot
Project overviewFull Garnet1 project overview with the Phoebe panel and saved simulation result visible
Closer lookPhoebe · Saved result
Phoebe answers the question about Garnet1’s latest circuit simulation with the completed Optical experiment, 201 wavelength points, two external ports, and its recorded wavelength range
Phoebe explains a saved circuit simulation.
Answers with context
Phoebe sees the whole picture: layouts, schematics, simulations, code, packages, and more across your Lumicron project.
You’re in control
Choose what Phoebe can access and review changes before applying them.

Answers depend on the available project information and AI provider.

Take the layout
to the lab.

Bring your layout to the probe station. Find devices, inspect layers, and measure on iPad.

Download on the App Store
Lumicron iPad companion showing a photonic chip layout with device pins

Follow your design
back to its source.

Link a DRC finding to its code. Inspect the data behind a component. Keep experiments close to the design.

Source links are available when the layout retains the information needed to trace them.

More than
a marker.

A source-linked DRC finding remembers its file, line, and revision. Lumicron checks the match before opening it in Script.

See it in action

How source navigation works

  1. 01 / LayoutSpot the issue

    DRC identifies the affected geometry.

  2. 02 / ProvenanceFind the source

    A source link records the file, line, and revision.

  3. 03 / ScriptOpen the line

    Open matching source in Script. Rerun DRC after edits.

What connects today?

Connected today

Source-linked DRC findings open in Script. Layout data can retain component, package, and source identity. Notebook keeps code snapshots, linked objects, and saved experiments.

Looking ahead

A complete tapeout history, automatic links for every verification result, and connections through fabrication and lab work are longer-term goals. Imported geometry needs source metadata to support source links.

Lumicron Alpha

What will you
design next?

Join the Alpha and help shape the future of Lumicron.

Try the Alpha

Tester approval and a license are required.