Frequently Asked Questions

Omaship is the creation and deployment layer for Sokrates and other agents. It gives agents Omaship Skills, a trusted Rails foundation, deploy path, and context layer for personal software, team workflows, and public applications.

Sokrates decides what should exist. Omaship makes it real as software your agent can deploy, inspect, and improve.

Omaship Skills are reusable playbooks for creating useful software types: approval flows, personal dashboards, directories, internal tools, onboarding checklists, lifecycle pages, and public applications.

They are the difference between giving an agent a blank repo and giving it a proven way to create something useful. AGENTS.md gives context. Omaship Skills give the agent repeatable creation judgment.

Engines are for the parts that are static, clear, and have been built hundreds of times before: the kind of building blocks many SaaS starter kits include.

Omaship Skills can use those engines when they fit, so Sokrates does not rebuild solved foundation pieces while creating the custom software you actually asked for.

Sokrates users who need their personal agent to create software around life, team, and public contexts.

Builders using AI coding agents who want a Rails foundation agents can navigate and humans can inspect.

Teams that want company workflows without forcing every need into a generic product shape.

It is not only scaffolding. Omaship creates the Rails surface and manages where it runs.

It is not a closed platform. You keep code, deployment, and infrastructure portable.

It is built for agents. Skills, context, conventions, and deploy paths are part of the product, so agents can come back later and understand what exists.

It is built for growth. Software can start personal, become useful for a team, and become public when it should.

A GitHub account, an agent workflow, and a deploy target with Docker support. Sokrates will use Omaship through the layer we expose for creation, inspection, and deployment.

Every Omaship project includes AGENTS.md context, and Omaship Skills give agents reusable guidance for the software they are creating.

The goal is that Sokrates can create a running software surface without a human rebuilding the foundation each time.

Exact public setup flows are still being shaped. The visible product is currently coming soon.

No. Rails' convention over configuration means AI coding agents know exactly where everything goes. Models in app/models, controllers in app/controllers—predictable structure that Claude Code and Cursor navigate effortlessly.

Describe the software you need. Sokrates can decide the shape, and Omaship gives it a foundation agents and humans can understand.

Every Omaship project includes AGENTS.md with project-specific context: architecture decisions, naming conventions, testing patterns, and deployment workflows. Omaship Skills add reusable playbooks for common app jobs, so agents do not have to rediscover the same product and implementation patterns every time.

Rails 8's convention over configuration means there's one obvious place for everything. AI agents don't guess—they follow conventions backed by 20 years of training data.

Convention over configuration. Rails has one way to structure a project. Next.js has hundreds. AI agents excel when patterns are predictable.

As DHH (creator of Rails) put it: "Convention over configuration set the path for 20+ years of great training data for AI to use today."

Y Combinator president Garry Tan called Rails + Claude Code "a crazy unlock." The framework was accidentally optimized for AI-assisted development.

Direct Omaship use needs technical comfort: running terminal commands, understanding what a database is, knowing what an API does. You don't need to write Ruby from scratch.

With Sokrates, the goal is different: you describe what should exist, and your personal agent uses Omaship underneath to create software around that context.

AI integration means software can call OpenAI, Claude, or Gemini APIs as a feature.

Agent optimization means the codebase is structured so agents can create, inspect, change, and deploy software without guessing.

Some tools add AI to a product. Omaship helps agents create the product itself and keep it understandable after launch.

Trust starts with clean code structure, checks, security practices, documented context, and portable deployment.

Omaship gives agents a foundation that humans can inspect. The result should not be a black box or a fragile prototype.

Yes. That is the point of the foundation. The code follows Rails conventions, lives in your repository, deploys to infrastructure you control, and can be reviewed by humans.

Agents can keep improving it, but they should not be the only ones able to understand it.

Personal software can become team software or public software. If deployment is locked to one platform, that growth path gets fragile.

Omaship uses standard Rails and Docker-based deployment so the software can move when your context changes.

Rails 8.1 with Hotwire (Turbo + Stimulus), Tailwind CSS, and Import Maps. No webpack, no complex JavaScript build process.

SQLite for everything—database, cache, background jobs, real-time updates. No Redis or PostgreSQL to manage.

Kamal 2.0 for deployment to any server with Docker support.

See full technical details →

Yes. SQLite handles most workloads beautifully (thousands of requests per second), but if you need PostgreSQL, migration is straightforward. Rails makes database switching simple.

Anywhere that runs Docker: Hetzner, DigitalOcean, AWS, Google Cloud, or your own hardware.

Kamal handles zero-downtime deploys, SSL certificates (via Let's Encrypt), and container orchestration automatically.

Omaship's core functionality is delivered as a Rails Engine. Update when you're ready:

bundle update omaship_base

Your customizations stay intact. Override any template or behavior you need.

Pricing is coming soon for all plans.

Plan limits are still coming soon. The product direction is personal software first, useful for your team, ready for the world when it should be.

• Agent-readable project context
• Rails foundation agents and humans can inspect
• Portable deployment
• Creation, inspection, and deployment workflows
• Commercial use where licensing allows

Final license details are coming soon with pricing.

We will offer support around setup and agent workflows as Omaship becomes available.

For ongoing help, the code is designed for agents and humans to inspect together.

Refund terms will be published with pricing.

Sokrates is meant to handle many custom software needs through Omaship. For direct Omaship users, custom help will be considered case by case.