Buy a pack
📦 Automation packs: $29 one-time per pack, $45 for YouTube Shorts + TikTok. See pricing →
Dex › Products

Getting started (Korean)

← All products

BUILDERLOG · CHANNEL AUTOMATION PACK

Blog Automation Pack

Code and operating guides for a Naver keyword queue, drafting, images, review, scheduling and RSS verification.

KRW 990/month or KRW 9,900/year per pack · Single-user license · External service costs are separate

Before you buy

This is code and documentation to configure on your computer. Account setup and terminal work are required. Setup services, AI subscriptions and API credits are not included. Setup time, views and income are not guaranteed.

One cloud CLI, Python 3.11+, Node 20+ and macOS/zsh. Publishing requires a Naver account and an authenticated Aside CLI profile. Ollama and image APIs depend on your production route.

Read requirements, costs and the user guide →

Delivery We send the install steps right after you subscribe (Mac and Windows/WSL). Updates install automatically · Refund policy · Terms · FAQ
🆓 Prefer to build it yourself? The free dex prompt Build a Blog Auto-Publishing Pipeline walks an AI through building it from scratch. The pack is the ready-to-run version with updates.

Subscribe on the Korean product page · KRW 990/month or KRW 9,900/year →

🔄 Bought this pack before the subscription launch?
  • You get free updates for the pack you bought for one year from the subscription launch date.
  • We email the install steps to your purchase email. After that, updates install automatically.

Do I need both Claude and Codex?

No. Start with one cloud CLI you can access. Claude Code needs eligible subscription access or Console API billing. Codex CLI supports an eligible ChatGPT plan or API billing. Subscription and API charges are different. The current Instagram pack also needs Ollama for local drafting.

Compare required/optional tools and official documentation →

Included

Your first run

  1. Check your environment, accounts and additional charges
  2. Install with the steps we send after you subscribe, then configure your settings
  3. Check with publishing, uploads, comment DMs and schedulers off
  4. Generate and review one output
  5. Verify integrations and permissions before enabling real publishing or scheduling

Precautions and support

Sign in and verify accounts yourself. Review facts, sources, asset rights and disclosures. Do not share keys, cookies or full .env files. Platform UI/API changes can require adapter updates. For support, provide the pack/version, OS, failed stage and error logs with secrets removed.

Step-by-step guide and troubleshooting → · Contact

Preview the five-step onboarding course (Korean) →