Tasukiba — Build the service together, grow together

Service features and how-to-use are on the user-facing page. What we keep here is the layer just before that: “why we build it,” “what we want to hold dear,” and “how you yourself can grow,” as compactly as possible.

To be honest: Tasukiba is currently developed by Suyama alone — a small project. Which means anyone joining now becomes an early member of the community, shaping the culture from the start.

The “zero to one” moment of a service only comes once.

What we actually want to build is this landscape:

Sunday night, you close the week with “I’m going to make tomorrow count” still in your chest. Monday morning, you walk into work feeling alive.

Once the time burnt on firefighting and information searching comes back, attention can finally turn from yourself to the organization around you — to mentoring people, to building psychological safety. Supporting that shift is, we believe, Tasukiba’s mission.

We also want this service to be a “third place” — alongside home and work.

While building the service, we want changes like these to happen for you, the developer. Read this as “a shared landscape we’d both like to head toward,” not as obligation.

Choosing to “graduate” mid-way to your own next step is a perfectly good outcome. This doesn’t have to be the destination.

These are the values Tasukiba holds dear. If they resonate with you, that means a lot.

1. Surfacing buried data is the essence

Not a tool that stores data — a tool that protects users’ creative time through semantic search × surfacing. We see this as the very core of the service.

2. We want to keep the UI simple, and user agency intact

Features can grow. The UI we want to keep as simple as possible. The freedom to change plans, cancel, export data — we want to respect user agency. We’d like to stay in the spirit of “neither newcomers nor leavers turned away.”

3. We care more about “keeping it going” than “maximizing profit”

Not profit maximization, but billing for sustainability. We are not aiming for short-term big growth. Patiently, over time, delivered to the people who actually need it.

4. Beside your day job — slowly, but seriously

We do not ask for excessive commitment. A rough baseline: one commit per month is enough. “Just reading this month” is welcome during busy seasons. At the same time, if you join, we hope it doesn’t end up as a “zero-progress ghost” state — leaning on each other and lasting a long time is what we’re hoping for.

5. We discuss, we don’t fear failure, we respect each other (the core of this community)

This is not just a slogan. Concretely, we want to grow these four into operating rules.

• Role and years of experience don’t change the weight of a voice — a beginner’s naive question often catches a design blind spot
• Critique code, not people — a review is “let’s find the next step together,” not a judgment stand
• A failure report is the entry point to a prevention discussion — never a place to assign blame. The reply is “thanks for telling me”
• See people off when they graduate, with a smile — leaving isn’t a “drop-out”; it’s “graduation to the next step,” and we honor it

Making the 5th item one we genuinely live by is, we believe, the foundation that lets Tasukiba’s developer community last.

If “I’m not confident in programming yet” describes you, there are still many ways in. Code is not the only contribution.

Even if you don’t yet know “where I’d fit” — just reach out. Finding it together, as we talk, is part of the fun.

For reference, here is the technology Tasukiba currently uses. You do not need to “already know” or “have touched” any of this. In fact, “lots of things I’ve never touched” is a feature, not a bug — it makes this a strong learning environment.

Versions and stack evolve continuously. Treat this as a May 2026 snapshot.

Click any area title to expand the details.

Browser
  ↓ HTTPS
Vercel (Next.js)
  ├─ Middleware (auth / RBAC)
  ├─ Route Handlers / Server Actions
  ├─ Service Layer  ← business logic lives here
  └─ Prisma + pg adapter
  ↓ Pooler (transaction mode)
Supabase PostgreSQL
  (extensions: pgvector, pg_trgm)
  ↓ External APIs
Brevo (email) / Voyage AI (embedding) / Anthropic (LLM)

To repeat: you do not need to know any of this up front. “Start with what you know” and “learn the unknown in the order you want to try it” are both welcome.

“Doesn’t fit” doesn’t mean “no.” It means maybe another place can put your passion and time to better use, right now. We share these honestly as signposts. If you’re unsure, please just talk to us first. Continuing after the conversation, or choosing a different path — both are welcome outcomes.

• You already have a clear service you want to build — Your own project or company may let your passion flow more directly. Realizing it within Tasukiba may be hard
• You’re chasing short-term big profit or rapid scaling — We chose “slowly, but seriously,” so the pace you’re hoping for may not match
• You see growing features as the point in itself — On the other hand, delivering high functionality through a simple UI is very welcome
• You’d rather debate “whose fault” a failure was — That style and our “thanks for telling me” culture may not line up right now. But if you’d like to try shifting, you’re welcome too

• Recruiting opens: 2026-06-01 (with general release)
• Before that: Say hi on GitHub Discussions any time
• GitHub: The code is already Public. Feel free to look around before deciding

The selection process will be designed later. For now, “let’s just talk first” is enough. Whatever your reason — to learn, to experience, to be involved — you’re welcome.

Hi, I’m Teppei Suyama. I work in software development for my day job — quality assurance and test design — and I’m currently growing this service on my own.

“You report a failure, and the reply is thank you.” That kind of workplace, that kind of community, is something I’ve personally longed for, for a long time. I want to grow the Tasukiba developer community into that kind of place.

While building the service, I’m still very much someone with room to grow, too. Not a fixed “I teach / you learn” dynamic — let’s build a place where we grow with each other.

I’m looking forward to the day you drop in to GitHub Discussions.