Skip to main content

Build your own developer platform

NovaNova
Set up eks-prod as a developer platform, the way this example does, and deploy latency-app.
Ask Nova

Rather not read it all? Ask Nova this. It walks you through each step and does the ones it can when you approve.

One path to production for every team. Your developers ship like it is a managed service; your platform team keeps control of the cloud, network, security, cost and history underneath. Every running image is scanned for known CVEs, which matters more now that AI writes more of the code. AstroPulse is the foundation, and Nova is your AI platform engineer.

What you're getting into​

AstroPulse runs the machinery and gives you the controls. Your platform and services are yours. Operating it is the hard part, and Nova, your AI platform engineer, runs it with you: it finds what broke and fixes it when you approve.

Internal developer platform: the platform once, every app the same way
Open zoom view

Four layers, top to bottom: your platform, your workloads, AstroPulse and your cloud. Nova runs on a rail outside them, working across every layer.

your AI platform engineerYOUR PLATFORMYour developer portal, CI and standards. That stays yours.YOUR WORKLOADSlatency-app and every team's services, each in its own namespace.DeploysVersions and rollbackHTTPS and DNSAccess and rolesVulnerability scanning (CVEs)Cost per appAdd-onsClustersYOUR CLOUDAWS, Google Cloud, Azure, or your own Kubernetes, in your account.

In words: your cloud and its Kubernetes cluster are the ground. AstroPulse runs on them as the platform layer: deploys, versions and rollback, HTTPS and DNS, access and roles, vulnerability scanning, cost, add-ons and clusters. Your teams' workloads run on AstroPulse, each in its own namespace, and your own developer platform (portal, CI, standards) sits on top. Nova, your AI platform engineer, works across every layer with your approval.

What AstroPulse does, and what you do​

Serves the layer above ↑
5Your servicelatency-app
4ReleasesVersions and rollback3Security and costCVEs and spend2NetworkAddress, HTTPS and DNS1ClusterKubernetes in your cloudRelies on the layer below ↓
  1. 5
    Your service

    AstroPulseruns it from its image.

    Youthe code and its image.

  2. 4
    Releases

    AstroPulserecords every release as a version and rolls back with the plan shown first.

    Youthe new image tag.

  3. 3
    Security and cost

    AstroPulsescans every running image for known CVEs and shows what each app costs.

    Younothing.

  4. 2
    Network

    AstroPulseroutes traffic, issues the certificate and writes the DNS record.

    Youa verified domain.

  5. 1
    Cluster

    AstroPulsecreates or connects the cluster and installs the add-ons.

    Youthe cloud account.

Follow the steps​

Anything else your platform needs, such as dashboards, alerting, a developer portal or a queue, is just another app: deploy it the same way, and it gets the same versions, rollback, scanning and cost.

  1. Set up the platform once
  2. Bring in your teams
  3. Deploy an app
  4. Scan for vulnerabilities
  5. Watch it run
  6. Ship a new version and roll back
  7. See what it costs

The design behind this example, with every choice and the platform apps' manifests: Developer platform blueprint.