<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Murat</title>
    <description>The latest articles on Forem by Murat (@flyingriverhorse).</description>
    <link>https://forem.com/flyingriverhorse</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3674852%2Fce78c019-b061-4fb7-8244-842c2a343a4e.jpg</url>
      <title>Forem: Murat</title>
      <link>https://forem.com/flyingriverhorse</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/flyingriverhorse"/>
    <language>en</language>
    <item>
      <title>From feature engineering to deployment: a local-first MLOps workflow with Skyulf</title>
      <dc:creator>Murat</dc:creator>
      <pubDate>Tue, 23 Dec 2025 09:53:56 +0000</pubDate>
      <link>https://forem.com/flyingriverhorse/from-feature-engineering-to-deployment-a-local-first-mlops-workflow-with-skyulf-140g</link>
      <guid>https://forem.com/flyingriverhorse/from-feature-engineering-to-deployment-a-local-first-mlops-workflow-with-skyulf-140g</guid>
      <description>&lt;p&gt;Most ML tooling assumes your data can live in someone else’s cloud, or that your team wants to assemble a stack of separate tools (orchestrator + tracking + deployment + UI) and spend weeks wiring everything together.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Who Skyulf is for&lt;/strong&gt;&lt;br&gt;
Skyulf is built for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Teams working with sensitive/regulated data&lt;/li&gt;
&lt;li&gt;People who want a &lt;strong&gt;local-first&lt;/strong&gt; workflow (laptop → server → on-prem)&lt;/li&gt;
&lt;li&gt;ML engineers and data scientists who prefer &lt;strong&gt;one integrated workflow&lt;/strong&gt; over a pile of disconnected components&lt;/li&gt;
&lt;li&gt;Anyone iterating quickly on models and wanting workflows that stay &lt;strong&gt;visible, repeatable, and easy to review&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;What you can do with Skyulf&lt;/strong&gt;&lt;br&gt;
Skyulf focuses on the end-to-end loop:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt; Ingest + explore data&lt;/li&gt;
&lt;li&gt; Feature engineering (visually, as a pipeline)&lt;/li&gt;
&lt;li&gt; Training (including background jobs)&lt;/li&gt;
&lt;li&gt; Deployment (self-hosted inference service)&lt;/li&gt;
&lt;li&gt; Verification with an API testing panel (send      JSON, view response/latency)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;pipeline → run → deploy → test API&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fs6fcjtkg8ag3afhk3ftq.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fs6fcjtkg8ag3afhk3ftq.jpg" alt=" " width="800" height="340"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8yh9r25t0s8028ubek15.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8yh9r25t0s8028ubek15.jpg" alt=" " width="800" height="345"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F10t6gio1s4cgvm42ek2c.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F10t6gio1s4cgvm42ek2c.jpg" alt=" " width="800" height="337"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why “visual pipelines” matter (beyond aesthetics)&lt;/strong&gt;&lt;br&gt;
A visual pipeline canvas isn’t just a pretty UI; it’s a way to make ML workflows:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;explainable (anyone can see what happens between raw data and model)&lt;/li&gt;
&lt;li&gt;repeatable (less tribal knowledge, fewer hidden scripts)&lt;/li&gt;
&lt;li&gt;reviewable (pipelines become artifacts you can share and iterate on)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;What’s next&lt;/strong&gt;&lt;br&gt;
Skyulf is open source and evolving. Near-term focus areas:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;more example pipelines (tabular, time-series, text/embeddings)&lt;/li&gt;
&lt;li&gt;more models&lt;/li&gt;
&lt;li&gt;better packaging for “one command” self-hosting&lt;/li&gt;
&lt;li&gt;integrations/export paths for teams already using other tools.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;u&gt;If you want to try it, start here:&lt;/u&gt;&lt;/p&gt;

&lt;p&gt;GitHub repo: &lt;a href="https://github.com/flyingriverhorse/Skyulf" rel="noopener noreferrer"&gt;https://github.com/flyingriverhorse/Skyulf&lt;/a&gt;&lt;br&gt;
Website/docs: &lt;a href="https://www.skyulf.com/" rel="noopener noreferrer"&gt;https://www.skyulf.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you only want the Python engine (no UI), for example, to integrate Skyulf into your own application or scripts, you can install skyulf-core directly via pip:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;pip install skyulf-core&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;If you run it and have feedback, open an issue, especially around onboarding and docs clarity.&lt;/p&gt;

</description>
      <category>mlops</category>
      <category>opensource</category>
      <category>datascience</category>
      <category>machinelearning</category>
    </item>
  </channel>
</rss>
