Skip to content
Parallax GET STARTED
PARALLAX KITS

The pieces for
your next project.

Code, configuration and instructions, kept together. Start with a Kit, adapt its contents, and combine it with the other pieces your project needs.

my-project.kit/
</>Application sourceBUILD
▤Dockerfile + compose.yamlRUN
↗Deployment manifestsDEPLOY
✓Release checklist + assetsLAUNCH
Illustrative contents. Native files retain their formats; this is not a required Kit directory layout.
COMPOSITION DIAGRAM

One project.
Several starting points.

A starter sets up the app. A feature adds a capability. Deployment files describe its destination. Launch material prepares its release.

Illustrative workflow. Cross-product Kit composition and deployment are in development. Starter, feature, run, deploy, startup and launch describe jobs within one Kit concept.

CLASS → TYPE → SPECIALIZATION

Find the kind of Kit
your project needs.

Class is the broad purpose. Type is the kind of Kit. Specialization is the specific job. The chart below shows examples, not an available package catalog.

Class

Build

StarterLaravel application
FeatureSubscription billing
Class

Operate

DeployKubernetes deployment
Class

Launch

ProductAndroid app
PublicationCookbook
FundraisingCommunity campaign
ACTUAL INTERFACE / ZEFRAM

From a Notes Kit
to an editable module.

The existing generator copies a Notes module, page and provider into your app. Choose browser storage or the PHP/database edition.

ZEFRAM Notes Kit setup interface showing the module name, edition selector and generated commands
Screenshot of the ZEFRAM browser Kit setup guide. Scaffolding runs in a configured ZEFRAM checkout. Click to inspect.

Try the existing generator.

slipstream kit notes Ideas --edition=js

Notes is the currently supported generator. The other examples above do not add new generators.

Explore ZEFRAM →
ANOTHER EXISTING CONTRACT

Context Kits

Positronic can package selected conversation messages and optional notes for a handoff, preserving the original archive. These are references, not executable deployment instructions. Availability depends on the product release.

Explore Positronic →
WHERE SOFTWARE RUNS

Run. Coordinate. Manage.

The intended progression is Nucleus → NEBULA → Positronic: runtime, orchestration, hosted platform. Docker → Kubernetes → hosted Kubernetes is a category comparison.

01 / NUCLEUS

On a machine.

Identity, approved workloads and your private fabric.

Explore Nucleus →
02 / NEBULA

Across machines.

Machine and network tools are in preview. Kubernetes provisioning and application deployment are in development.

Explore NEBULA →
03 / POSITRONIC

As a managed service.

Current plans cover managed machines. Hosted Kubernetes is planned and is not included in those plans.

Explore Positronic →
YOUR NEXT PROJECT

What do you want to make?

DISCUSS YOUR PROJECT →